Enhanced claim validation

ABSTRACT

Enhanced product tracking, in which a data collection interface is established between a first supply management device and a transaction database, the data collection interface providing the transaction database with access to identification data and event data, the identification data uniquely identifying a pharmaceutical, and the event data relating to a supply chain process step for the pharmaceutical. Tracking also includes receiving a tracking request for formatted identification data and/or event data from a second supply management device; and establishing a data conversion interface between the second supply management device and the identification data and/or the event data, the data conversion interface providing the second supply management device with access to the identification data and/or the event data, according to the tracking request.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of (and incorporates herein byreference) U.S. patent application Ser. No. 11/839,921, filed Aug. 16,2007, which is a continuation of U.S. patent application Ser. No.11/348,014, filed on Feb. 6, 2006 (now U.S. Pat. No. 7,321,310, issuedJan. 22, 2008), which is a continuation of U.S. patent application Ser.No. 10/364,849, filed on Feb. 11, 2003 (now U.S. Pat. No. 6,995,675,issued on Feb. 7, 2006), which was a continuation-in-part of U.S. patentapplication Ser. No. 10/073,485 filed Feb. 11, 2002 (now U.S. Pat. No.6,664,897, issued on Dec. 16, 2003), which was a continuation-in-part ofU.S. patent application Ser. No. 09/544,388, filed on Apr. 6, 2000 (nowU.S. Pat. No. 6,346,885, issued on Feb. 12, 2002), which was a divisionof U.S. patent application Ser. No. 09/036,564, filed Mar. 9, 1998 (nowU.S. Pat. No. 6,342,839, issued on Jan. 29, 2002). The disclosures ofthe prior applications are considered part of (and are incorporated byreference in) the disclosure of this application.

BACKGROUND

1. Field of Invention

The present invention relates to a system, computer program product andmethod for tracking processing events for a meat animal from itsconception to its consumption, by using data entry devices that minimizekeyboard entry and multiple interconnected databases such that aparticular animal history can provide both quality assurance sourceverification and performance tracking.

2. Description of Related Art

Overview

There is a need, for both economic and quality assurance reasons, for anefficient and cost-effective method for identifying and trackinglivestock, and for the monitoring of the processing of those livestock.Throughout the livestock production and processing cycle, there is aneed for more detailed information so that ranchers, stockmen, feedlots,packers, distributors retailers, consumers, and others can make informeddecisions about factors and variables such as genetics, herd management,purchasing, feed strategies, and ship dates. Producers who improve theiranimal performance can realize greater returns with performance basedcompensation when accurate information about the history and the valueof each animal is easily available.

There is also a growing concern about quality assurance in the livestockprocessing cycle; and there is an opportunity for producers andprocessors who can establish that quality assurance to improve theircompensation. Effective quality assurance programs such as HACCP, orHazards Analysis and Critical Control Points, programs require accurateand timely information about the history of each animal. Thecertification of organic food products, hormone-free food products, andnon-genetically modified food products requires an accurate history ofthose food products.

The Beef Industry

The beef industry is a good example of the livestock industry.Traditionally, there are four segments to the U.S. beef industry: thecow/calf producer, the stockman, the feedlot, and the packer.

The commercial cow/calf producer has a herd of mother cows that are usedto produce calves. The cows are bred to bulls so that, ideally, each cowhas a new calf each year. The calf crop that is produced each year isused primarily for meat production, with some calves retained asreplacements for the herd. The calves are usually weaned from theirmothers at between six and eight months of age. The traditional producerwill sell his animals once they are weaned. Typically, the mainobjectives of the producer are to have a calf from each cow each year;to have healthy, vigorous calves with the highest weaning weights at thelowest cost; and to produce the best meat, by factors such as tendernessand taste, at the lowest cost.

In order to support these objectives, the producer is interested inefficient systems for identifying and tracking individual animals asthey rotate through the producer's pastures; identifying which animalshave a good calving history; monitoring the performance of variouspastures; recording calf birth date and birth weight statistics andtracking the genetic history of each animal; evaluating the performanceof calves from particular cows or bulls; recording the weaning date andweaning weight of each animal; and recording treatments, vaccinations,and other significant events that have occurred in the animal's life.

The stockman receives the weaned calves when they weigh approximately500 pounds, and feeds them for four to six months until they weigh 700to 800 pounds. The stockman's typical objective is to add weight as fastas possible, while keeping the animals healthy. In order to supportthese objectives, the stockman is interested in collecting and usinginformation such as identifying and tracking individual animals as theyrotate through the stockman's pastures; recording beginning, ending, andperiodic weight measurements and treatments; and recording vaccinations,movement and ownership changes, and other significant events that haveoccurred in the animal's life in order to track of the success oftreatments as well as to eliminate duplicate treatments.

After the stockman phase, the animals are typically sent to a feedlotwhere they are fed a high-energy diet for about 150 days. At thefeedlot, the cattle are in a finishing stage, where the main objectiveis to add pounds quickly while keeping the animals healthy. The cattlewill be finished when they reach a weight of approximately 1,100 to1,200 pounds. The feedlot is interested in animal weight gain, animalhealth, the effectiveness of various feed ration formulations, thecharacteristics of the feed consumed by an animal, required waitingperiods on shipping animals after drug treatments, and animal origin andhistory.

The slaughter facility or packer typically slaughters the animal andthen chills, ages and cuts the carcass into the various cuts of meat andpacks those cuts for shipment to distributors and retailers. The packeralso provides grade and yield ratings for the carcass. Important qualityfactors include the live animal weight, the carcass weight, a chilledweight; and the yield, grade, and quality of the carcass and carcassdefects. The information collected by the packer is important to all ofthe upstream participants, because it allows them to adjust theirmanagement practices based on the actual quality and economic result foreach animal. The upstream data is important to the packer because itpermits the packer to select animals that produce the results desired byits customers.

Typically, each of these four segments, the cow/calf producer, thestockman, the feedlot, and the packer, have attempted to optimize theirown operations, and there has been relatively little emphasis oncooperative optimization efforts. There is a growing recognition acrossthese industry segments, however, that for both quality assurancereasons and for the improvement of the industry in general, it isdesirable to improve data collection and data management. An object ofthe present invention is to provide improved data collection and datamanagement and reporting.

Variability and Quality Control

There is variability in individual animal production efficiency and inindividual carcass quality characteristics such as weight, frame size,muscling, fat content, marbling, and feed efficiency. This variation isdue to a combination of genetic factors and environmental factors suchas health and drug treatments, nutrition, growth history, andenvironmental and management factors such as geography, weather, andanimal husbandry. Many of the genetic and environmental factors can becontrolled or managed to improve both quality and economic return oninvestment if accurate historical information were available throughoutthe production cycle.

The livestock industry has recognized that certain livestock species andbreeds outperform other species during production and processing. Theprior art has used data collection systems and statistical analysis ofdata related to livestock breeds in order to identify higher performancebreeds. There is a need to extend this data collection so thatindividual producers can make informed decisions about individualanimals in order to further improve their herds.

Electronic Identification

Although it is possible to use manual identification methods forlivestock and to employ manual data entry methods, it is desirable toautomate the identification and data entry in order to reduce expenseand to improve accuracy of the data. These devices typically produceeither a unique alphanumeric code or a unique decimal code.

Electronic identification devices and systems have provided a goodmethod for providing identification of livestock. Typically, electronicidentification systems utilize a passive electronic identificationdevice that is induced to transmit its identification signal by anexternally radiating source. These passive electronic identificationdevices may be a transponder carried with the individual animal on acollar as illustrated and described in Carroll U.S. Pat. No. 4,475,481,issued Oct. 9, 1984, entitled “Identification System” and in Kuzara U.S.Pat. No. 4,463,353, issued Jul. 31, 1984, entitled “Animal Feeding andMonitoring System”; in an ear tag such as those commercially availablefrom Destron/Fearing, Inc., Allflex USA, Inc. and Avid Marketing, Inc.;in a transponder implanted in the animal as illustrated and described inPollack U.S. Pat. No. 4,854,328, issued Aug. 8, 1989, entitled “AnimalMonitoring Telltale and Information System” and in Hanton U.S. Pat. No.4,262,632, issued Apr. 21, 1981, entitled “Electronic LivestockIdentification System”; or in a bolus such as illustrated and describedin U.S. Pat. No. 4,262,632, issued Apr. 21, 1981, entitled “ElectronicLivestock Identification System” by John P. Hanton and Harley A. Leach.

Although electronic identification through radio frequencyidentification (RFID) tags or barcodes are used in some phases of thelivestock production cycle, there is a need to provide a means forindividual animal identification throughout the production cycle and tominimize the difficulty of data entry throughout the industry, byinterfacing with identification technologies such as RFID, barcode,retina scan, iris scan, DNA, and visual identification.

RFID Readers

Several RFID readers are commercially available, typically from thetransponder suppliers, including models from Destron/Fearing, Inc.,Allflex USA, Inc., Avid Marketing, Inc., and Tag Tracker™ from InfoClipLLC.

The prior art includes RFID readers that can distinguish multiple typesof RFID transponders as illustrated and described in U.S. Pat. No.5,235,326, issued Aug. 10, 1993, “Multi-Mode Identification System” toMichael L. Beigel, Nathaniel Polish, and Robert E. Malm.

Databases and Management Systems

At different stages of the production cycle, there are differentdatabases, which exist for different business purposes. The rancher willtypically maintain his own database, a stockman will have an inventorysystem, a feedlot will have a management database, and a packer willhave its own inventory and management system. There is also a trendtoward larger marketing alliance or national databases that include somedata from each of these industry segments.

U.S. Pat. No. 5,322,034, which issued Jun. 21, 1994 to Richard L.Willham, for a “Livestock Record System” describes a method for storingthe individual animal's identification and performance data on aprogrammable electronic identification and data storage module carriedwith the animal. An object of the present invention is to provide alow-cost per animal system for obtaining and maintaining sourceverification and performance databases that are independent of theanimal.

U.S. Pat. No. 5,315,505 issued to William C. Pratt on May 24, 1994 for a“Method and System for Providing Animal Health Histories and TrackingInventory of Drugs” describes a method and system for providing improveddrug treatment to selected animals in a retained group. A computersystem is used to provide an operator with the health and drug treatmenthistory of an animal. With this information and a diagnosis of theanimal's health condition, a drug treatment is chosen. The diagnosis andtreatment are entered into the computer system to update the animal'shealth and treatment history. An object of the present invention is toprovide complete source verification and performance databases for allkey livestock events.

U.S. Pat. No. 5,673,647 for a “Cattle Management Method and System”,issued on Oct. 7, 1997 to William C. Pratt, describes an automatedmethod and system for providing individual animal electronicidentification, measurement and value based management of cattle in alarge cattle feedlot. That method includes individual animalidentification, a computer system, and multiple measurements coupledwith a cattle handling and sorting system. An object of the Pratt patentwas to build a feedlot database to more accurately identify and measurecharacteristics such as weight, so that subsequent animals could beproduced and fed for more effective value-based selection and managementof the animals. In particular, that database related to calculations foreconomic management of feeding and shipping to permit optimum weightgains and feedlot ship dates. Whereas the feedlot patent disclosedidentifying a particular animal on arrival at the feedlot, an object ofthe present invention is to track individual animals throughout theproduction cycle and to maintain performance and source verificationdata in the least disruptive manner to existing databases and managementsystems.

SUMMARY OF THE INVENTION

The present invention relates to a system, computer program product andmethod for identifying, tracking and monitoring livestock. The resultinginformation will provide a basis for entities in a supply chain, such asthe producer, the stockman, the feedlot, and the packer to make informedherd management and operational decisions.

An object of the present invention is to provide an effective datacollection and database management methodology in the livestockindustry. The present invention includes a database computer programproduct for maintenance and entry of data associated with livestock.Data may be entered into the invention in the form of events, which aresignificant occurrences in the livestock production and processingcycle, and include items such as vaccinations, medications, treatments,live weight, weight gain, slaughter date and carcass weight. Using thecomputer program product, the user may: enter new animals into thedatabase; look up information, including identifying information andevents, on animals which have already been input into the database; andrun queries on information contained on the database. Using the computerprogram product, the user may also: apply an individual event to a groupof animals; apply multiple events to a group of animals; determine ananimal's average daily weight gain; determine the best time for ananimal to go to slaughter based on target weight; manage hardwaredevices that support automated entry of the animal's identification anddata associated with that animal; use his or her own local terminologywhen applying events to an animal's record; import data into thedatabase after collecting the data from another application; send datato a spreadsheet while pointing the data to specific worksheets andcells within the spreadsheet; transfer animal data from one database toanother on the same machine or within a network such as the world wideweb; transfer animal records from one entity to another; and communicatewith other databases for sharing information concerning the livestock.

With the addition of RFID transponders for each animal and“event/detail” transponders, the computer program product becomes partof a system such that an RFID reader may be used to read thetransponders thereby facilitating automated entry of individual animalidentification and automated entry of events and details associated witha particular animal. Events and event details may be aliased, and dataentry simplified, such as through RFID, bar codes, function keys, ormemory buttons. With the addition of radio frequency wirelesscommunications, the system becomes even more convenient and easy to use.The system also includes audio feedback to confirm receipt of data intothe system and multiple interconnected databases to facilitate thetransfer and maintenance of animal data. One result of this invention isthat quality assurance source verification data for individual animalswill be available throughout the production and processing cycle. Thissource verification will include the ability to implement HACCP plans.The source verification provides an opportunity for enhanced productvalue through improved quality assurance and food safety.

Another result of this data collection and management invention is thatanimal-specific performance information can be provided to the producer,the stockman, and the feedlot, and the packer so that those entities canmake informed herd management and operational decisions. Improvedinformation availability permits all segments of a supply chain such asthe livestock industry to reduce cost of operations while improvingproduct quality. The opportunities for process improvement range fromavoiding duplicate treatments; to selecting more cost effective breedingstock; to selecting more cost effective feeds. As part of the productionprocess, other entities, which are not usually in the chain of title toan animal, also have an interest in a portion of the data. Veterinarianscan access the health history, nutritionists can access the feed andhealth history, and bankers can know the location of their collateral.Authorization levels designate what information may be made available tothese entities.

The data collection and management capability is provided in a seamlessand non-intrusive manner to all participants. The system encourages thecollection and storage of data by putting the majority of the datacollection and management process in the background, transparent to theuser.

Through the current invention, the complete history of an animal isequally available throughout the production cycle, and both sourceverification and specific performance information are accessible withoutunnecessary duplication of data.

One result of this data collection and management invention is thatquality assurance and source verification data for individual animalswill be available throughout the production cycle. This sourceverification will include the ability to implement HACCP plans. Thesource verification provides an opportunity for enhanced product valuethrough improved quality assurance and food safety.

Another result of this data collection and management invention is thatspecific information can be provided throughout the supply chain so thatentities in the supply chain can make informed management andoperational decisions. Improved information availability permitssegments of the supply chain to reduce their cost of operations whileimproving product quality. In the livestock industry, some opportunitiesfor process improvement include avoiding duplicate treatments; selectingmore cost effective breeding stock; and selecting more cost effectivefeeds.

Although the invention is described in the context of beef cattle, it isnot so limited. It should be apparent to those skilled in the art thatthe invention can be modified, without departing from its principles,for other livestock including cattle, swine, sheep, goats, and fowl; andto other agricultural products including grain, fruits, and feedstuffs.

DESCRIPTION OF FIGURES

These and other features, aspects, and advantages of the presentinvention will become better understood with regard to the followingdescription, appended claims, and accompanying drawings where:

FIG. 1 is a schematic of a paper information entry embodiment of theinformation management system.

FIG. 2 is a schematic illustrating a protocol converter to exchangeinformation with an existing livestock management software program.

FIG. 3 is a schematic showing a wired connection between the RFID readerand a host computer.

FIG. 4 is a schematic showing a wireless radio frequency datacommunication (RFDC) connection between the RFID reader and a hostcomputer.

FIG. 5 is a schematic showing a wireless radio frequency datacommunication (RFDC) connection to a base station transmitter/receiverlocated between the RFID reader and a host computer.

FIG. 6 represents a schematic of the physical flow of cattle and theinformation flow for the beef cattle supply chain.

FIG. 7 is a schematic showing data movement and storage.

FIG. 8 is a schematic illustrating email file updates to a database.

FIG. 9 is a schematic showing a wireless radio frequency datacommunication (RFDC) connection between the RFID reader and a hostcomputer and additional livestock databases.

FIG. 10 is a schematic showing a cabled connection between the RFIDreader and a data concentrator device and a wireless connection to ahost computer and additional livestock databases.

FIG. 11 is a schematic showing a wireless radio frequency datacommunication (RFDC) connection between multiple RFID readers and a dataconcentrator device and a wireless connection to a host computer andadditional livestock databases.

FIG. 12 is a schematic of an embodiment.

FIG. 13 is a schematic overview of the components in an embodiment ofthe BeefLink program.

FIG. 14 illustrates the use of multiple servers in the embodiment ofFIG. 13.

FIG. 15 illustrates the GlobalCore server in the embodiment of FIG. 13.

FIG. 16 illustrates the EventCore server in the embodiment of FIG. 13.

FIG. 17 illustrates the DeviceCore server in the embodiment of FIG. 13.

FIG. 18 illustrates the DeviceCore and AgInfoPorts components in theembodiment of FIG. 13.

FIG. 19 illustrates the core components in the embodiment of FIG. 13.

FIG. 20 illustrates the dynamic event object in the embodiment of FIG.13.

FIG. 21 illustrates the data collection and real time data lookupcomponents in the embodiment of FIG. 13.

FIG. 22 illustrates event creation in the embodiment of FIG. 13.

FIG. 23 illustrates group data creation in the embodiment of FIG. 13.

FIG. 24 illustrates user interface in the embodiment of FIG. 13.

FIG. 25 illustrates data management functions in the embodiment of FIG.13.

FIG. 26 illustrates the Individual Animal Manager in the embodiment ofFIG. 13.

FIG. 27 illustrates the Share, Switch, Route, and Interface componentsin the embodiment of FIG. 13.

FIG. 28 illustrates selection and query components in the embodiment ofFIG. 13.

FIG. 29 illustrates the data sharing and representation components inthe embodiment of FIG. 13.

FIG. 30 illustrates the AgInfoPorts component in the embodiment of FIG.13.

FIG. 31 illustrates the electronic file transfer components in theembodiment of FIG. 13.

FIG. 32 illustrates the ShrinkCalculator processing component in theembodiment of FIG. 13.

FIG. 33 illustrates interfaces to third party software in the embodimentof FIG. 13.

FIG. 34 illustrates the ETL components in the embodiment of FIG. 13.

FIG. 35 illustrates the report and analyze components in the embodimentof FIG. 13.

FIG. 36 summarizes user interface, data collection, and data sharingfunctions of an embodiment.

FIG. 37 is a flowchart for data collection in the embodiment of FIG. 36.

FIG. 38 is a flowchart for the event server in the embodiment of FIG.36.

FIG. 39 is a flowchart for the transfer of animal data in the embodimentof FIG. 36.

FIG. 40 is a flowchart for the transfer of an animal in the embodimentof FIG. 36.

FIG. 41 is a flowchart for updating a database in the embodiment of FIG.36.

FIG. 42 is a flowchart for hardware interface in the embodiment of FIG.36.

FIG. 43 is a flowchart for defining a regimen in the embodiment of FIG.36.

FIG. 44 is a flowchart for applying data to a group in the embodiment ofFIG. 36.

FIG. 45 is a flowchart for translation in the embodiment of FIG. 36.

FIG. 46 is a flowchart for average daily gain determination in theembodiment of FIG. 36.

FIG. 47 is a flowchart for week to slaughter determination in theembodiment of FIG. 36.

FIG. 48 is a flowchart for data formatting in the embodiment of FIG. 36.

FIG. 49 is a flowchart for email transfer in the embodiment of FIG. 36.

FIG. 50 is a flowchart for spreadsheet data injection in the embodimentof FIG. 36.

FIG. 51 is a sample Select Kill Lot screen for an example AgInfoLink.netsystem.

FIG. 52 is a sample Lot Overview screen for an example AgInfoLink.netsystem.

FIG. 53 is a sample Lot Comparison screen for an example AgInfoLink.netsystem.

FIG. 54 is a sample Individual Animal Report screen for an exampleAgInfoLink.net system.

FIG. 55 is a sample Microsoft Excel Data Export screen for an exampleAgInfoLink.net system.

FIG. 56 is a sample Select Kill Lot screen for an example AgInfoLink.netsystem.

FIG. 57 is a sample 2-View Comparison screen for an exampleAgInfoLink.net system.

FIG. 58 is a sample 4-View Comparison screen for an exampleAgInfoLink.net system.

FIG. 59 shows a transactional data structure event table.

FIG. 60 illustrates a linking of events in a food tracing application.

FIG. 61 illustrates an Animal event tree-structure.

FIG. 62A is a schematic diagram showing functional groups of layeredprotocols and services linking the information backbone to anapplication program.

FIG. 62B is a schematic diagram showing an example of layered protocolsand services linking the information backbone to an application program.

FIG. 63 is a data flow chart for the event accounting layer.

DETAILED DESCRIPTION OF THE INVENTION Wireless Embodiment

An embodiment of the computer system disclosed herein operates using aprogrammable IBM®-compatible laptop host computer. Other hosts includeother devices and operating systems including hand held devices.Referring now to FIG. 4 illustrating this embodiment for the computersystem, the host computer 10 includes a central processing unit; acoprocessor; a display device; a random access memory; a read onlymemory; a first data storage means; a second data storage means; a thirddata storage means; memory controllers; motherboard resources; akeyboard; a sound card and driver; external power supply with DCconnection; and a USB or serial port. BEEFLINK™ data collectionsoftware, a means for accessing the BEEFLINK™ database, a means foraccessing portions of the BEEFLINK™ software by hyperlink, and anoperating system run on the host computer 10. A speaker 11 is connectedto the host computer 10 such that information recorded into theBEEFLINK™ data collection software's database by the reader or by keyentry may be audibly confirmed. When the host computer 10 confirms thatany information, including a transponder reading, was handled within theBEEFLINK data collection software, the reading of a .WAV file isinitiated in the host computer and the .WAV file is played through thePC sound card to the speaker 11.

Example Wireless Communication and Data Consolidation

In order to better understand the invention, key portions of theinvention are described as examples, and larger examples are used toshow how the pieces are integrated in the invention.

Referring now to FIG. 5, an animal is uniquely identified by means of aradio frequency identification (RFID) ear tag 32 or other type ofidentifier such as bar code, iris or retinal, DNA, or visual identifier.The preferred identification is an RFID ear tag such as those providedby Y-Tex Corporation, SFK Technology, Destron/Fearing, Inc., AllflexUSA, Inc, or Avid Marketing, Inc. Alternately, the identification may beby means of an RFID implant, a rumen bolus, or a collar fitting on aneck or leg.

This RFID identification is typically applied at the first opportunityto pen and work the animals, such as at an initial immunization orbranding. The identification typically remains with the animal until thetime of its slaughter. The RFID identification typically will havepreviously been applied to older breeding animals.

As the animal is typically restrained in a working chute, itsidentification may be determined by means of an RFID reader 30. Thisidentification is accomplished by placing the reader near, typicallywithin six inches, of an RFID ear tag or implant transponder. The rumenbolus has a greater range. The preferred reader is described in moredetail in an alternative embodiment described below.

Typical events performed on the animal may also be captured withoutkeyboard entry by means of a Work Card 31 which is a collection ofcommon tasks or events that are assigned unique RFID transponder codes,indicated as transponders 42, 43 and 44, such that the reader candesignate an event by reading the transponder associated with an event.This reading is accomplished by placing the reader near the transponder.Alternately, the event transponders can be placed separately atconvenient locations in the work area. The event transponders willtypically be labeled with text or symbols to identify the event. Eventsmay also be imported from other programs such as third party software,and may be manually entered such as with a Cattle Card™ system describedin another example.

The reader communicates by means of radio frequency data communications(RFDC) to a radio frequency receiver/transmitter that is connected byserial or USB port 50 a to the computer. The reader may be connected bydirect cable linkage to the port, or preferably, will communicate byradio frequency data communications means 52 c from a base stationtransmitter/receiver located on the reader to a transmitter/receiverconnected to port 50 a.

Other livestock measurement data can be collected through serial or USBport connection such as a scale 54, a thermometer 55, or an ultrasoundmeasurement device 56. Various output devices including audio feedbackmeans such as a speaker 57 or a headphone 59, an LED display 58, aprinter 60, or a UPC Barcode printer or reader 61 can be connected tothe computer. The audio feedback means may be a specified .wav file, adefault .wav file, or a simple “ding”.

The data is received by the computer through the base station. Thepreferred communication is a radio frequency link 52 between atransmitter/receiver 71 attached to the data concentrator and atransmitter/receiver 72 attached to an interface board in the computer.The computer may include a keyboard, a monitor, and a speaker 11. Datamay be stored to a diskette 13, but will typically be transferred bymeans of a modem. The computer is preferably an IBM compatible laptop ordesktop computer. Beeflink™ software runs on the computer to provide thelivestock data entry management function. The computer is connected bymeans of network adapter or modem 12 to other computers as describedmore fully in other example embodiments.

This embodiment permits a portable reader to be used in a remotelocation to gather animal and event data and to communicate that data toa host computer.

The host computer preferably has a Windows 98 or above operating system,and at least one serial or USB port.

Example Single Port Communication to Remote Radio FrequencyIdentification Readers and Data Collection Devices

Referring now to FIG. 5, in this embodiment, a remotetransmitter/receiver 53 a is incorporated into each of one or more RFIDreaders, and is in two-way wireless communication 52 c to a base station50. Multiple readers can be used for a single base station; and the basestation requires only one input port 10 c to the computer 10. Other datainput devices such as scales 54 and thermometers 55 communicate with thebase station through a remote for each such input device. When a remotedevice is installed, the Base Station Unit detects its presence andassigns a device identification.

This information is relayed to the Host PC via the cabled connection(USB, RS485 or RS232). The Host PC makes the software applicationassociation through Beeflink or through included InfoClip driversoftware. Two-way communication between the host and the remote permitconfiguration such as specifying the baud rate of a device once theremote is detected. Multiple channels permit a one-to-many relationshipbetween the host computer and the remotes.

An improved RFID reader 53 b includes a microprocessor which scrubs thedata and assigns a unique device number to the data. The communicationutilizes spread spectrum 2.4 gHz with frequency hopping. An internaldipole antenna on the reader has a range of up to about 0.5 miles fromthe base station. The transceiver inside the reader can be procured witha RF connector which would allow the use of another internal antennawhich would increase the RFDC range. An optional external antenna has arange of over 20 miles (Note this antenna configuration requires FCCapproval). The same type of transmitter/receiver and firmware can beused to transmit data from the other measurement devices. The basestation preferably has both a USB port 50 a and a RS485 port 50 b, whichallows applications requiring more than 3 meters of cabling between thebase station's USB port and the host computer to use the RS485 portwhich has a range of about 1700 feet. At the computer, a RS485 to USBport converter 10 b is provided in order to use the computer's USB port10 c.

The low battery indicator light on the reader can be used as a statusindicator of the connection with the base station, so that a green lightindicates a good connection, a yellow light indicates a marginalconnection, and a red light indicates a lack of connection. At lowbattery, the light flashes red. A global positioning system may beincluded in the base station to identify the location of the basestation at the time it receives data.

Example The Beeflink™ Data Collection and Management System

BeefLink is a data cattle collection and data management implementationof the current invention. The BeefLink system is easily adaptable toother livestock species and other individual units of production such ascarcass, batch, or lots, and cuts of meat, with the major change beingthe definition of industry-specific events.

BeefLink is comprised of hardware and software to permit the user toscan radio frequency identification (RFID) ear tags, implants, collars,or boli with radio frequency identification scan readers; to enter newanimals; to look up information on existing animals; to input newevents; and to run queries on the work done. One objective of thesoftware is to display pertinent data on each animal and add new eventsto the record in the least intrusive manner. The new animal records andevents recorded are uploaded and incorporated into a larger database.Communication with the distributed databases allows the user to receivedownstream animal performance data at his own computer.

The preferred components of the system include a computer, a basestation transmitter/receiver for communication to remote wirelessdevices including readers and measurement devices, RFID transponders oneach animal, and RFID Work Cards.

Referring to FIG. 10 which is a schematic of one wireless embodiment ofa data collection system, the BeefLink software runs on the hostcomputer 10 which may be either laptop or desktop computer. The computeris in contact, by means of wireless radio frequency communication 52,with one or more readers and measurement devices. The wirelessconnection is accomplished by means of a transmitter/receiver 72connected to the host computer, and a transmitter/receiver 71.

In the embodiment shown, the reader 30 is connected through a cable 38and a serial port to the base station 50. In alternate embodiments, thereader is connected to the base station 50 by wireless radio frequencydata communication. The reader may read an animal RFID transponder 32and a Work Card 31, which consists of multiple event RFID transponders.The host computer 10 is connected to the Internet 77 by means of anetwork adapter or modem 12. Data is distributed to other databases byreal time communication over the Internet, batch updates via Agil emailfiles, or with physical media.

Other computers 79 and 80 containing other databases 78 and 81 may beconnected to the Internet by means of a modem 76, such that data may betransferred over the Internet between the host computer and the othercomputers. Other embodiments illustrate the use of the BeefLink softwareon both simpler and more complex data gathering systems.

Double-clicking the BeefLink icon on the Windows Desktop display startsthe BeefLink program. When the Company ID, the User ID, and the Passwordare entered on the Authorization Screen display, the program can beaccessed.

In order to speed data entry, Action Tags are used to enter most events.Rather than typing in events at the computer keyboard, events areassigned to the Action Tags ahead of time so that the tags are simplyscanned with the same reader used to scan animals in order to enterevents or update fields in an animal's record. For instance, if cows arebeing checked for pregnancy, An Action Tag will be assigned beforehandfor both the “pregnant” and “open” result so that the user can scan thecow and the appropriate pregnancy Action Tag when the result is known.Another example is that certain animals being processed are vaccinatedfor shipping fever. An Action Tag is assigned to the shipping fevervaccination event so that when animals get the vaccine, the user canscan the animal and the shipping fever Action Tag in order to record theevent.

The Action Tags are typically affixed to a Work Card alongside theircorresponding event labels. The Work Card can be placed in strategiclocations such as on the side of a working chute or with the vaccine ortreatment bottle to which they are assigned. Most common events will beidentified with Action Tags when the user receives the system. The usermay, however, add to or change existing events through a work cardeditor.

Each event can have one or more default details associated with it. Forinstance, the event “LOCATION” might have three different details suchas PEN-1, PEN-2, and NORTH 4000, that can be used to record changes inanimals' locations. The user may edit work cards by adding or editingevents associated with a unique identifier; and can designate aparticular sound file to provide audio confirmation when selected.

Core events are included for process steps and data collectionthroughout the supply chain including: Abort, Assess Animal, AssessAnimal-Health, Assess Animal-Sick, Assign Value, Birth, Birth-Est,Brand, Bred-Al, Bred-Bull-Grp, Bred-Bull-Ind, Breed, Buller, BullOut,Calving, Carcass, Carcass Weight, Clock-In, Clock-Out, Clone, Colot,DamID, Diagnose, Died, Dry Conversion Rate, Feed, Feedlot In, FeedlotOut, Feed-ration-Start, Finance, Group, HACCP, Hedge, Hedge-Remove,Implant, Implant-Remove, Incident, Incident-Removed, Insure, Irradiate,Location, Metal Tag, Origin, Packer-In, Packer-Out, PregChk,Production_Destination, Purchase, Railer, RegNum, Retag,Retailer_Feedback, Roundup, Sell, Set Alliance, Sex, SireID,Slaughter_Date, Spay, Stocker-In, Stocker-Out, Synchronize, Tag Brand,Trailer, Transfer, Treat, Vaccinate, Visual Color, Visual ID, Wean,Weather, Weigh, Weigh-Average, Wt-Birth, Wt-Birth-Est, Wt Est, WtFeedin, Wt-Feedout, Wt-Packerin, Wt-Packerout, Wt-Purchase, Wt-Sell,Wt-StockerIn, Wt-Stocker Out, and Wt Wean. It is desirable to utilizecore events when appropriate because they update fields in the database.If none of the default events apply, the user may key in a new event.

The most efficient way to record repetitive events that occur tomultiple animals is to assign animals to logical groups and to recordthe events to all animals in the group as “regimens” or “group events”.

The form also allows for entering multiple events and details beforeupdating the group. For instance, if every animal in a group had achange in their ration and received a group treatment in their feed, theuser could select and “Add” both events, and then update the records.

When all animals being processed receive the same treatments, but do notbelong to a particular group, the regimen option should be used. Aregimen is an event or group of event and associated event details thatare common to a group of animals. For example, the regimen could be“sex” and the event detail “heifer” for a group of females. In moresophisticated examples, an entire treatment protocol of vaccines anddeworming dosages can be specified, where a vaccination dosage is aspecified child event to a particular parent vaccine. Separate regimensmight be specified for steers than for heifers. This feature permits theuser to pre-select events for all animals. Then, as the animals arescanned, each animal's record is updated with the default events anddetails, until the function is turned off.

For example, a stockman operation is receiving 50 new calves from aranch, and the stockman needs to record the origin of each animal, thevaccines given each animal, the identity of the group, and the locationwhere the animals will be going.

One way to set up a regimen is to pre-define each input to be made asdescribed above for a particular vaccine and dosage. Alternately, theregimen may permit the user to scan or otherwise input the data at thetime of the event. For example, a regimen is specified as being avaccination with a user specified vaccine, and a child event dosageaccepts a user-specified dosage. The regimen prompts the user to inputthe type of vaccine and then prompts the user for the dosage given tothe current animal. An identifier such as an RFID device or barcode maybe placed on work card along with various dosages and various vaccinesto permit the user to provide the scan inputs without keyboard entry.

Any time that different events need to be recorded on each animal, theevents must be applied individually. For example, if cows are beingchecked for pregnancy, the results vary and need to be recordedindividually. Another example is when sick animals are treated at afeedlot—different treatments are applied and recorded individually.Recording individual events is automated by using the Work Carddescribed earlier. After an animal is scanned, the events on the cardthat apply are scanned and thus recorded. This method can be used inconjunction with default events—all animals receive the default eventsand some also receive additional individual events.

If animals are receiving new sequential visual and/or metal ear tags,they can be sequenced automatically so that the tags increment as eachanimal is scanned. To set the starting sequence for new tags, the usercan click on the “Sequence New Ear Tags” button at the Command Centerand enter a tag prefix or Starting Tag Number. An EditSequence utilityis provided, which enables the user to predefine sequences such asvisual id number, carcass number, or order number.

Once the starting ear tag sequences have been set, they are ready to usewhen the user needs them. The user may activate sequencing as a defaultevent or with an Action Tag.

Before working cattle, the user may either verify or make changes to hisWork Card through “Edit Work Card” from the start menu. In order toverify that an Action Tag is actually associated with the correct event,the user will scan the Action Tag. If the tag has been assigned as anevent, the user will get a duplicate error-trapping message. By the “OK”button on the error message, or pressing the Enter key, the screen willdisplay the event currently associated with the Action Tag.

If the event associated with the Action Tag is correct, then the usercan continue scanning other Action Tags that need to be verified. If theuser needs to change the event associated with the tag, the user erasesthe current entry and enters a new event and detail for the deletedAction Tag.

When the user is ready to work animals, which will usually be done atthe working chute, the user must intentionally turn on the ApplyRegimenupon entity identification scan button. Events will not be appliedunless this button is clicked. This way, the user won't set up defaultsand forget to turn them on, or assign default events by mistake.

With the RFID reader cabled or wireless radio cabled to a communicationport, the user is ready to start scanning animals.

For example, if the first animal scanned has existing records in thesystem, the display screen will show those data fields. The scroll barmay be used to view additional fields. The bottom half of the screenshows all events recorded during the animal's lifetime. If the userscans a “TREAT” Action Tag with “IVOMEC” for the detail and changes theanimal's location to Pen 50, the records will be updated.

Although the user may watch the results of his scans on the screen, it'snot necessary to see the screen while processing animals. A feedbackacknowledgement in the form of a light or sound may be sent to the userto indicate that the scans have gone through correctly. This feedbackcan be in the form of a light or sound generation, or it may be directedthrough a serial port to an external device. Typically the user will geta positive feedback signal in the form of a burst of light and an audioacknowledgement when he reads an animal that exists. The user will alsoget the acknowledgement when he scans an event.

When an animal is scanned, the user is provided a confirmation. Ananimal may be scanned more than once, and a confirmation will beprovided, but the data will only be entered once.

If all of the animals being worked are new to the system, some defaultswill probably be entered into the system. For instance, if all animalshave the same estimated birth date, the date can be set as a default andadded automatically to the birth date field of each new animal scanned.The same default function could be used for origin, location, or group.

If, however, the animals have varying birth dates or birth years, theavailable birth dates can be assigned to Action Tags, using the eventsetup form. The user can use BIRTHDATE as the event and the date as thedetail. As each animal is scanned, the correct birth date tag is scannedand assigned to the animal.

If actual birth dates are used and there are many possible entries, theuser will enter the dates individually. The user will Set up an ActionTag event with BIRTHDATE as the event and KEY as the detail. To add aspecific birth date to the animal's record, the user will scan theanimal and the Action Tag. The user is then prompted to key in the birthdate.

Entering non-sequential visible or metal tags may be done in the samemanner. If an animal loses its RFID tag the animal can be re-tagged, andan Action Tag with “RETAG” as the event can be used to replace the oldtag references. The system can be used with visual ID tags and barcodetags, but RFID transponder ear tags are the preferred identificationmethod.

Animal body weights can be entered in several ways. First of all, thereare many different types of weights that can be recorded. Periodicweights are the most common, but other specific weights such as weaningweight, stocker-in weight, feedlot-in weight, etc. can be specificallynoted.

Weights can either be recorded automatically with an electronic scale,or keyed in using a keyboard or other peripheral method. If the weightsare to be gathered automatically, the user should identify the portthrough which the weights will be entering. The user will select theappropriate weight event and select the detail, either AUTO for a scaleconnected to the system, or KEY if weights will be keyed in. If theevent is a default to be collected on all animals on a connected scale,the weights will be collected automatically. If the default is the keyedweight, each time an animal is scanned, the user will enter a weight. Ifthe user is not weighing all animals, the same events can be scanned asAction Tags.

In addition to setting default events at the computer, defaults can beassigned, turned on and turned off in the field such as at the workingchute. For example, if the user has fifty animals being worked thatreceive the same events—the events can be identified and turned on whileworking the cattle. If the next group of animals being worked receivedifferent regimens, then the current regimens can be appended or clearedand new ones assigned.

If the user mistakenly assigns events to an animal and wishes to deletethem, he can scan the delete last event to remove events one at a time,or delete all to remove all events for a working session. Events canonly be deleted for the current animal. Any events that are correctshould be rescanned. This function also works well if the user isassigning default events to a majority of the animals, but wants to skipcertain animals. The user can simply scan the Delete Event tag after theanimal that does not receive the events is scanned.

Data can be viewed on Animal Manager. The animal record contains somebasic header information, as well as an on-going list of events,weights, and animal movements. To review an individual animal, the userscans the transponder or types in the visual or metal ear tag number.The events listed on the animals record can be sorted in order of theevents, the details, or by date. The user can also do a quick review ofall recorded weights or locations by clicking the applicable radiobutton on the bottom of the form.

The information collected on all animals can be reviewed by clicking onthe “Work Done” button in the Review section of the Data CollectionCenter. This form allows the user to query the data that has beencollected by selecting the field and the criteria of the search.

Events recorded on each animal will typically be exported to a largerdatabase. The larger database will not only store information on otheranimals, but will store information on one entity's animals that havebeen transferred to other entities. Enterprise BeefLink is typicallywired or wirelessly connected to the Internet, or is run in adisconnected mode with batch updates though ShareData utility andelectronic transfer such as email update. The user may click on the“Export” button at the Command Center to create the file for uploadingto the larger database. The export file is in the form of an event file,with special entries for new animals added to the local database.

Many events can be identified by a single code and a single set ofassociated data. Other events such as an animal vaccination eventrequire additional data. The user can read an event detail transponder,such as vaccine type, and can then read sub-detail events such as adosage or batch that he wants appended to the main detail.

This is accomplished by identifying each event detail as either aSTANDARD or SUB detail. If the detail is a SUB event, then it willappend to the last standard detail scanned. For instance, along with avaccine, a dosage may be specified.

Example A Paper-Based Embodiment

FIG. 1 illustrates a paper-based embodiment of the BeefLink datacollection software. In this case, animal identification would beobtained from a visual tag, such as an ear tag, and that visualidentification would be written on a paper log 14. All event data andmeasurement data would be recorded on the log sheet and then entered bykeyboard or regimens or groups into the BeefLink software running on thehost computer 10. The modem 12 in this embodiment permits the hostcomputer to establish data transfer capability with other computers, andthe removable disk 13 provides a data backup capability.

Although the data entry would be cumbersome for large numbers ofanimals, this paper system may be more affordable for smaller producers.

The producer may elect to install only visual identification or toinstall a tag that is both visual and RFID.

If an RFID transponder was attached to an animal, the producer would beresponsible for manually entering the code to the computer, so that thecode would be correlated to the visual tag identification.

Alternately, it is possible to operate the BeefLink software on thebasis of the visual identification, or preferably a longer, uniqueidentification key assigned to the animal. In that event, an RFID devicemay be attached downstream, and the new RFID code would be assigned tothe animal.

U.S. Pat. No. 6,211,789 issued to Oldham and Curkendall describes CattleCard™ embodiments of this invention designed to support manual datacollection in the early phases of livestock production. Events common toa group of animals are typically noted on a form such as the Cattle Cardenvelope, so that the common events can be entered as a regimen.

Example A Direct Reader Embodiment

FIG. 3 illustrates a simple embodiment of the BeefLink data collectionsoftware with an RFID reader 30, which was linked by cable 33 to a hostcomputer 10. In this case, animal identification would be obtained froman RFID transponder 32, and Work Cards 31 where RFID event transpondersare used to record events.

The speaker 11 provides a feedback means to confirm the receipt ofanimal and event data by the computer.

The modem 12 in this embodiment permits the host computer to establishdata transfer capability with other computers, and the removable disk 13provides a data backup capability.

This approach would typically be used by relatively small producers whocould complete their livestock work sessions in a relatively short time,such as the battery life of a notebook computer.

Example Simple Wireless Reader Embodiment

FIG. 4 illustrates a simple embodiment of the BeefLink data collectionsoftware with a radio frequency wireless connection 40 between the RFIDreader 30 and the host computer 10.

In this case, animal identification would be obtained from an RFIDtransponder 32, and Work Cards 31 with RFID event transponders are usedto record events.

The speaker 11 provides a feedback means to confirm the receipt ofanimal and event data by the computer.

The modem 12 in this embodiment permits the host computer to establishdata transfer capability with other computers, and the removable disk 13provides a data backup capability.

Example Existing System Communication

FIG. 2 illustrates the ability of the BeefLink software running on ahost computer 10 to accept data from an existing livestock managementsystem 20 or to update the management system data with information fromBeefLink. If the existing management system software was not running onthe host computer, the host computer could establish a link to theexisting management system computer by means of a modem 12 and either adirect link or an Internet connection. An event import tool convertscolumnar data to an event database.

FIG. 9 illustrates this existing system or existing databasecommunication in a wireless reader embodiment. The RFID reader 30communicates through RFDC transmitter/receivers 36 and 71.

Existing or downstream database 78 or existing management systemsoftware running on a computer 79 may be accessed through the hostcomputer modem 12 by either Internet transfer 77 or by direct modemconnection between the computers.

FIG. 6 is a schematic of the physical flow of cattle and the informationflow for the beef cattle supply chain. The current invention permits thecapturing and sharing of information from each step in the supply chain,and establishes interfaces with existing third party software packages20 a-20 i, third party ERP software packages 22, and third partybusiness to business software packages 23. In the supply chain,seedstock 82 is typically sold to cow-calf producers 83 through auctionfacilities or e-commerce at step 100. The cow-calf producers typicallysell calves to stockers 84 or feedlots through auction facilities ore-commerce at step 101. The stocker typically adds weight to thosecalves and sells them to a feedlot 85, through direct sale, auctionfacilities or e-commerce at step 102. In some cases, the stocker orcow-calf operator may retain ownership of the calves at the feedlot, sothat there is not a sale at that point. The feedlot continues to addweight to the calves and sells them to a packer 86 at step 103. Thepacker may produce packages of beef 87, leather products 88,pharmaceutical products 89, and processed beef products 90 such ascooked, smoked, or ground beef. The beef products 87 and 90 aretypically sold to food brokers, distributors, cutters, supermarkets, orfood service companies 91 and 92 in forward contract arrangements 93 oron the spot market 94 to customers 92 b. Throughout the supply chain,third parties 95 such as banks, pharmaceutical companies, veterinarians,and livestock marketing associations have an interest in portions of theinformation.

The current invention includes hardware and software data collectiontools 105 to capture information at the seedstock stage 82 and to sharethat information with one or more third party seedstock software package20. The Pony Express Relay Database™(PERD) 606, which functions as adata backbone, provides access to information collected at all stages inthe supply chain, and provides an interface 107 to the third partyseedstock software package 20 to permit information to be shared fromthe third party software to PERD, and from PERD to the third partysoftware. Similarly, at each of the other steps in the supply chain, theinvention provides data collection interfaces 107 to third partysoftware packages 20 and interfaces between those packages and PERD 606.The system also supports the collection of DNA information 96, includingat the packer 86, and barcode information systems 97 such as in theleather 88, pharmaceutical 89, and cook/smoke/grind 90 operations.

The system also provides interfaces 107 to reporting and viewingutilities 108 so that the data and information can be monitored by thirdparties including banks, insurance companies, animal health companies,veterinarians, cattle procurement, and livestock marketing associations.

In order to link the individual animal or animals to the consumer orretailer 98, the system accepts a packer lot number identification 99and generates a request 109 to run a DNA sequence for a specified lot,and interfaces that request to PERD at step 110. PERD then interfaces107 to the tracking software which generates the specific test requestsfor a lot 111 or animal 112.

The data collection components typically include data collectionhardware such as RFID readers, electronic scales, and ultrasound;Beeflink™ data collection software, real-time feedback components; andutilities to format the data according to desired third party softwareformats. When the user does not have a computer, a manual input systemsuch as Cattle Card™ is used to collect the data, which is subsequentlyinput into the BeefLink software.

The data conversion interfaces typically include authentication andcertification software components to validate data; extraction,transfer, and loading tools to support data marts for specific reportingneeds; reporting tools for generating reports not provided by the thirdparty software; and data mining and data mart tools.

These middle-ware components, data collection and data conversion, andETL tools permit sharing by importing or exporting individual managementinformation.

Referring now to FIG. 7, which is a schematic showing data movement andstorage, data is collected at step 116 from entities such as cow/calfoperations 83, auction sales 101, stockers 84, feeders 85, packers 86,and retailers or consumers 98. The data collection may be throughBeefLink software, data cards 14 such as Cattle Card™, or third partysoftware 20. The data is pushed at step 117 to PERD transactiondatabases 118 and “411” data warehouses 119. The “411” data warehousesmonitors the location of individual animal data. Data is extracted atstep 120 into data marts 121 such as real-time escrow transactiondatabase 122, food safety tracking database 123, carcass reportsrelational database 124, epidemiology database 125, AgInfoSheetstransaction server 126, pharmaceutical database 127, e-commerce database128, or other transaction or relational database 129, including thirdparty software applications 131. Data may be pulled from the data martsat step 130 by the processing supply chain entities that collected thedata or by third parties, and third party databases that are providedsecurity clearance to access that data. The “411” data warehouses 119provides a brokering private network links service protocol layer 665 tothe information backbone 606 as described below and as described in FIG.62.

Example Information Backbone with Layered Protocols and Services

The PERD 606 and interfaces 107 which are described in FIG. 6 may beimplemented as a data backbone or information backbone with a series oflayered protocols and services such as illustrated in FIG. 62. Thelayered protocols and services are grouped by function includinginterconnectivity 650, audit trail 654, data processing 657, datarouting 662, and data reporting and archiving 666.

In this example, the interconnectivity 650 layers include applicationprogram interface 651, secure socket layer 652, and data exchangeprotocol 653. The audit trail 654 layers include an event tamper-evidentlayer 655 and a data integrity layer 656. The data processing 657 layersinclude a data filtering layer 658, a data map/translate/normalize layer659, event accounting layer 660, and a data benchmarking layer 661. Thedata routing 662 layers include a data permission layer 663, a datarouting layer 664, and brokering private network links service layer665. The data reporting and archiving 666 layers include an archive andchange reporting layer 667 and an aggregation, consolidation, reportinglayer 668.

The application program interface (API) 651 provides the basicinterconnectivity from the third-party application, such as provided atthe supply chain entities 82-100 in FIG. 6, and the information backbone606 using standard API tools. This service provides a simplified methodof sending data into and retrieving data from the third partyapplication.

The secure socket layer (SSL) 652 provides basic data security andauthentication services for the transport of data from the third-partyapplication to the information backbone over the Internet. This serviceprovides a very basic level of data security protection and assurancethat the person sending or receiving the data is the person they purportto be, but does not provide an audit trail for the data.

The data exchange protocol 653 such as the XML standard provides amethod of expressing data in a common format.

The application program interface (API) 651, the Secure Socket Layer(SSL) 652, and the data exchange protocol 653 are conventional toolsthat provide basic networking services. This embodiment includesadditional layers of services to implement an effective information ordata backbone for agriculture and food.

The event tamper-evident layer 655 detects whether a single record hashad its data altered. There may be strong economic incentive for foodchain participants to alter data after a food safety episode in order toreduce their potential liability, such as changing some laboratory testresult for a truckload of tomatoes. In this embodiment, the informationbackbone stores data in such a way that if data are changed eitherduring transit through the backbone or in some application, this changewill become evident.

The data integrity layer 656 provides an assurance that entire recordshave not been added or removed in an unauthorized manner from thedatabase. The data integrity can be monitored by the data and time thedata was entered, the entity that input the data, and the record entrymethod for the data was entered. There may be strong economic incentivesfor certain supply chain participants to either add records post-hoc toa potential liability episode, or to remove records. The data integritylayer helps prevent this problem. The combination of the data integritylayer and the tamper-evident layer provide a complete, trusted audittrail of all events and activities in the system.

The data filtering layer 658 manages the information that can be sharedfrom one node in the information backbone network to another. Becausethe information backbone may be implemented as distributed databasesrather than a centralized database server, rules are desirable tospecify what class of data or what data elements within a data class canbe sent either up or downstream to other servers within the same privatedata sharing network. For example, the server that is executing theinformation backbone at the producer segment may be told by theinformation backbone administrator at that segment to not share costdata with the aggregators but to share this information with selectedproducers. The benefit from this service layer is that data can becollected and transferred to the information backbone with the assurancethat it will not be accessible to whole other classes of users.

The data map/translate/normalize layer 659 provides three servicefunctions—data mapping, data translation which could include actuallanguage translation, and the normalization of data in terms of commonunits of measurement.

The event accounting layer 660 is used to provide a method for keepingtrack of paying suppliers of information and charging users ofinformation. This layer may or may not be activated for a given privatedata sharing network. The benefit from this service layer is that itprovides a method for members of the private data sharing network to becompensated for entering data, substantially increasing the probabilitythat data are entered and that it is of high quality.

The data benchmarking layer 661 is a specialized data mart for providingcomparison data for each member of the supply chain to determine howthey are doing in comparison with their peers. The particular segmentsof the chain to be benchmarked, and the reported data are configurablebecause certain private data sharing networks will not want to benchmarkcertain activities.

The data permission layer 663 is used to determine which user can seewhat data. The layer provides data confidentiality.

The data routing layer 664 is used to route information to authorizedusers such as prior owners, future owners, or other authorized partiessuch as crop consultants, bankers, nutritionists, insurance companies,veterinarians, and other consultants. The benefit from this layer isthat only the right users see the data for which they are authorized.

The brokering private network links service layer 665 provides a methodfor connecting separate private data sharing networks, such as the AGIL411, without exposing any of the data within a network outside of thatnetwork. The primary benefit is to create a series of “water-tight” datastructures that ensure high levels of confidentiality for participantswithin a private data sharing network.

The archive and change reporting layer 667 enables the retention of apersistent image of each event that enters the backbone, so that thebackbone can provide a “shadow” backup of the data, and provide a way torestore data structures in the event of catastrophic system failure.This persistent image also allows the backbone to determine what'spossibly been changed when an event has gone into a third-partyapplication and returns modified.

The aggregation, consolidation, reporting layer 668 allows for the rapidcreation of data marts for presenting the data in different formats todifferent members of the chain.

Example Multiple Reader Locations

FIG. 11 illustrates a wireless reader configuration where the dataconcentrator 50 receives data from multiple RFID readers indicated byreaders 30 and 45. This type of configuration is desirable in largeroperations where there may be more than one livestock working area at agiven time. In this case, a larger antenna 63 may be necessary at thedata concentrator, and it may be desirable to have a keyboard 261 andmonitor 262 connected to the data concentrator.

Example Description of Embodiment

Referring now to FIG. 12, in this embodiment the components of the datacollection and management system include unique Radio FrequencyIdentification (RFID) transponders for each animal; a Work Card of RFIDtransponders to identify livestock events, an RFID Reader that canidentify the animal and event RFID transponders; a wireless RFDCcommunication between the reader and a base station; wired or wirelessconnections to a scale, a thermometer, an ultrasound measurement device,and an output device, a wireless RFDC communication between the dataconcentrator unit and the host computer, BeefLink™ Data CollectionSoftware; and etl interfaces.

Radio Frequency Identification (RFID) Transponders

Although the data collection system can operate manually with visualanimal identification, the preferred operation is with Radio FrequencyIdentification (RFID) transponders 32 in the form of electronic eartags, implants, boli or neck or leg collars to provide uniqueidentification for each animal. Although ear tags and implants are themost common devices, a bolus transponder has been used successfully as atamper-proof means of identification of cattle. The bolus transponderhas the potential capability of measuring temperature and pH within theanimal. The RFID transponders contain a small antenna attached to anintegrated circuit that stores a unique identification number. Unlikebar codes, RFID transponders do not require line-of-sight to be read,the transponder simply needs to come into the proximity of an RFIDreader.

RFID Reader

The RFID reader 30 will typically be a stationary reader at high volumeat the packer or feedlot operations and portable readers at theprocessing points. Stationary readers will typically be connected to ahost computer by means of a cable, but a wireless connection may also beused for stationary readers. The portable readers will typically use awireless connection to the computer. The Readers emit a low radiofrequency, typically a 134.2 kHz signal that excites the passivetransponder in the event or animal identification tag and the deviceresponds at a second frequency. Once excited, the transponder respondsback to the reader via radio frequency with a digital signalrepresenting its unique identification. The reader decodes the signal,displays the identification, and sends the identification to thecomputer.

Work Card and Event Action Tag

A Work Card 31 with RFID transponders 41, 42 and 43 provide livestockevent identification so that events can be read by the RFID readerrather than entered by keyboard.

The user may select one or more event cards for the anticipated worksession. Other event tags may be affixed at other convenient locationsin the work area, such as around the processing chute. The tags on thework card have the name or symbol label for the corresponding events sothat the person working the cattle can quickly scan the appropriateevent when it occurs.

BeefLink™ Data Collection Software

The BeefLink™ software running on the computer 10 validates inputs fromthe various devices, notifies the user of the data received, stores theresults, and converts the data into meaningful information. In addition,the software manages the transfers of the local data via modem toregional and national databases for storage and further analysis, andmanages the access to downstream processing, performance, and qualitydata.

Database Architecture and Data Transfer

Data collected at the local level can provide only limited managementinformation to the producer because the producer needs to know theperformance results in order to manage accurately for the future. As thedata is transferred to a regional or national database, indicated as 78,it can become more powerful. In many cases, the animals change handsduring the production cycle. In order to get results back to theproducers and growers of the livestock, these upstream participants musthave the ability to pull information about the animals that thedownstream participants enter into the system. Likewise, the downstreamparticipants such as feedlots and packers need to review information onthe animals that they are receiving. It is also these large databasesthat allow for the source verification for food safety issues.

The local software at each participant's facility routinely sends fileupdates to an alliance or national database using modem transfer throughthe Internet. With the proper security clearance, users can query thedata on their own cattle even after they have been transferred or sold,and this is the information useful for future management decisions.Producers are also able to purchase reports that benchmark their animalsagainst a compilation of blind data from other producers. For example,producers may compare their operations with operations of a similarsize, geographic region, or breed for quality characteristics such asthe tenderness score.

Once the animal reaches the slaughter plant, the same RFID transponderis used for identification. Stationary readers or handheld readers areused to read the transponders and to identify and sequence thecarcasses. Data such as carcass weight, grade, and yield are collectedand added to packer's management system, and that data can be accessedthrough the animal's identification.

Authorization Levels

In the preferred embodiment, authorization levels are provided forvarious entities such as a consultant, veterinarian, nutritionist,insurance agent, or banker, can access information according to thatentity's authorization level.

Source Verification/Performance Tracking

In the preferred embodiment, the RFID tags, and visual identificationtags are correlated so that at any point in the livestock cycle,historical data is available to any entity in the chain of title for thelivestock.

At the packing plant, the animal's identification is used to recordactual carcass quality data for the animal. The data can include overallevaluation of the carcass as well as information about the amount andquality of particular cuts or products derived from the carcass. Thiscorrelation of individual animal identification to actual carcass andproduct quality data permits the packer to compensate the producer orfeedlot according to the actual quality of the product.

The producer benefits both by having the potential to receive a greaterreturn for higher quality livestock, and by obtaining information whichwill permit more-informed decisions on herd management. For instance,bulls or cows that produce calves with good yields and quality will bepreferred for retention in the herd over bulls or cows that producecalves with lower yields or lower quality.

Whereas the prior art requires transmission of packer information backto the feedlot or to producers, the present invention permits entitiesin the chain of ownership to have access to the data associated with ananimal. An additional objective of the invention is to provide SourceVerification by making historical data for the animal available to thepacker. This Source Verification will preferably include certifiedquality control programs such as HACCP plans.

DESCRIPTION OF EMBODIMENTS Software Components

One aspect of the BeefLink software is a transaction focus, rather thana relational database orientation. Although, in some applications,working relational databases may be constructed by utilities fromdistributed transactional databases, the BeefLink architecture alsosupports decentralized, transactional databases. Transactional data arethe building blocks of the information system.

In this embodiment, the software has an object-oriented architecture,and is comprised of blocks of code called components. The componentsprovide a building block framework for various software applications, sothat the components may be re-used from one application to the next.Sub-components are blocks of code that may be incorporated into multiplecomponents. The discussion below describes these components andsub-components by their functional task. Referring to FIG. 13, which isa schematic overview of the components of this embodiment of theBeefLink program 190, the components are grouped, for discussionpurposes, into common core components 200; Data Collection/Real-TimeData Lookup components 400; Share, Switch, Route, Interface (“SSRI”)components 500; Extract, Transform, Load (“ETL”) components 600; andReport & Analyze Data components 700. The components are typicallyconnected to a plurality of hardware or software servers 300. Many ofthese components are used in more than one of these categories.

In this discussion, the events relate to animals. In other embodiments,an event may be an item, commodity, or concept, and these components andarchitecture are appropriate for a variety of applications where theobjects, the actions on the objects, and the database entries andqueries, are distributed over time and geography. In these applications,an event-based architecture is robust and practical.

Servers

FIG. 14 illustrates the use of multiple servers 300 in this embodiment.In other embodiments, these functions may be performed on one or moreservers.

GlobalCore 310 is a Windows-based client side Active-X serverresponsible for managing connections to local or networked componentinformation. It provides the language-specific data needed for userinterfaces, text messages, database connection information, anduser-configurable settings. The server provides a centralized locationfor component messages, and allows distinct business components tointer-operate. The server provides standardized methods for creating andmanipulating information that is global to all components on the system;and notifies connected business components of any changes made to theglobal information.

Referring now to FIG. 15, the GlobalCore server 310 performs security311 to validate connection authorization and to confirm communicationencryption; creation and manipulation 312 to provide standardizedmethods for creating and modifying global data; and notification 313 toensure that business components are notified before, during, and afterany creation or modification of global information. The notificationupdates persistent storage 314, which may reside elsewhere, to abstractthe physical storage methods from component applications including DBMS,ODBMS, or flat file format on either the client-side or the server-side.The global server permits component messaging 315 to send messages toother components and to log important processes. The component messagingprovides a common messaging interface, global process completionlogging, and error logging.

Referring again to FIG. 14, EventCore 320 is a Windows-based client sideActive-X server responsible for creation, manipulation, storage,notification and access to collections of events. All businesscomponents that use, or need knowledge of, event-oriented data do so byestablishing a connection to the EventCore. The server providesstandardized methods for creating and modifying events; and ensures thatevents can be translated and represented by user-configurable languages.The server ensures that transactions, especially those representingquantifiable data, are normalized to a world-common standard. Itenforces data to be created with acceptable values, limits, rangesand/or formats; and sends both synchronous and asynchronous messages toconnected business components, allowing them to modify events beforethey are created, and respond to modified events. The Event Corecomponent is an example of a data map/translate/normalize layer 659 tothe information backbone 606 as described in the INFORMATION BACKBONEWITH LAYERED PROTOCOLS AND SERVICES example above and as described inFIG. 62.

Referring now to FIG. 16, the EventCore 320 performs security 321 tovalidate connection authorization and to confirm communicationencryption; creation and manipulation 324 to provide standardizedmethods for creating and modifying global data, specifically event data;translation 325 to permit representation in user-configurable languagesand storage in a core language; normalization 326 to ensure thattransactions such as measurement, quantities, and values are created ina standardized and normalized format to permit functional and accurateprocessing by business rules; validation 327 to ensure that objects ofeach type are created within acceptable values, limits, ranges, orformats; and notification 328 to ensure that business components arenotified before, during, and after any creation or modification of eventinformation. Persistent storage 314 is updated during the notificationprocess. The event server also includes data access views 322 to provideconnected or disconnected views into subsets of event data. The dataaccess views also access the persistent storage. The component messagingprovides a common messaging interface, process completion logging, anderror logging.

Referring again to FIG. 14, DeviceCore 330 is a client side Active-XWindows-based server responsible for managing connections to local ornetworked hardware devices. All business components that use, or needknowledge of, hardware devices connected to the system do so byestablishing a connection to this server. It provides standardizedmethods for creating and modifying device data, and sends bothsynchronous and asynchronous messages to connected business components,allowing them to modify device messages before other components respondto their information.

Referring now to FIG. 17, the DeviceCore 330 includes creation andmanipulation 332 to provide standardized methods for creating andmodifying data; and notification 333.

Referring now to FIG. 18, the DeviceCore 330 includesSerialDeviceComponents 331 which interface with AgInfoPorts 554 tomanage the connection to local or networked devices such as an RFIDreader 30, scale 54, or ultrasound 56. The DeviceCore performsmanipulation, and notification functions and allows AgInfoPorts 554 tosend data to the IndividualAnimalManager 482 component and other thirdparty components.

The Core Components

Referring to FIG. 19, the following core components are used throughoutthe data collection, SSRI, ETL, and reporting functions. Id 210 is aunique identification number used to identify events, animals, regimens,images, and other entities. In one embodiment, the identification is acombination of machine identification and universal time that is createdusing the Microsoft GUID (Globally Unique Identifier) data type whichallows for any machine in the world to create 1000 unique identifiersper second.

In this embodiment of an event database, an Event 220 is a group of dataused to represent a discrete transaction against an animal. The eventstructure allows for any type of data, including binary data, to beattached to an animal or item, and allows for that data to be uniquelyidentified, classified, time-stamped, audited, and related to other datafor that animal or item.

Referring now to FIG. 20, the dynamic event object 220 includes uniqueidentification 221 of the event with respect to parent, child, orsibling relationships to other event objects; security 222 whichvalidates all data stored within the event object; type 223 whichspecifies the classification of the commodity such as animal, grain, orfruit; auditing 224 which includes the date and time of the transaction,the date and time of creating the event, the transaction creationmethod, and the transaction origin; and object data 225 which identifiesthe transaction type and supports the storage of any serializable datasuch as strings, numeric, data, time, or a binary stream or file. Inthis embodiment, a dynamic event object is a transaction-based dataelement that can be related to an animal, person, place, group, orobject. Some examples of events include animal data such as weight orbreed; group data such as ranch or shipping date; and customerinformation such as address or purchase order. The event representationpermits description of a series of processing steps which result in thecompletion of a specific function or activity, so that a set of actionsmay be treated as a single unit of work.

Referring again to FIG. 19, DataSource 230 abstracts a data source suchas a comma-delimited file, an ISAM database, a Client/Server SQLdatabase, or other data source. All data manipulation requests, such asqueries and manipulations, are routed through this component. In thisembodiment, MicroSoft Data Access Objects™ and MicroSoft Active DataObjects™ are encapsulated to provide this level of abstraction.

The EventTranslator 240 allows users or administrators to providealternative language-specific representations for event types anddetails. This capability allows component interfaces to displayinformation using the preferred language of the end user, whilepreserving the standardized/normalized value of the event informationstored in the database. All events are stored in the database using a“Core” language. When these events, and their values, are displayed in auser interface, they are translated into the native language of thetarget user. The EventCore uses this component to translate user- orlanguage-specific events back into their “Core” values.

As systems expand, so do their storage needs. SchemaSniffer 250 is asub-component which validates existing storage capabilities, and scalesthose capabilities as required by the system components. SchemaSnifferprovides for the automated scalability of database structures byensuring that storage will be available for storing the minimumrequirements of all components. Components using SchemaSniffer have theability to create and enhance their storage specifications withoutworrying about the effects it will have on other system components—eventhose using the same storage location.

Entity Registration 260 connects to the GlobalCore to configure thedynamic database connections used by other components and the EventCore.This includes managing user information such as entity id, password, andlanguage; and the connection properties for the Events Database,component database, sound file, and report templates.

Data Collection/Real-Time Data Lookup Components

The data collection and real time data lookup components are illustratedin FIG. 21, and discussed below in terms of event creation 420 as shownin FIG. 22; group data creation 440 as shown in FIG. 23, user interface460 as shown in FIG. 24, and data management 480 functions as shown inFIG. 25.

Referring now to FIG. 22, ApplyEvent 422 is an ActiveX control that usesthe EventCore to create events, and through EventCore notificationsupport the creation of special events, which are those events thatrequire device information, keyboard input, or work card scans tocomplete the gathering of event information. Special events also includehandling automatic sequences; transaction rollbacks such as “undo allevents”; and animal processing such as “select previous animal”. This isthe primary event creation component used by the Individual AnimalManager.

EventDrillDown 424 is an ActiveX control used to show, in detail, aspecific individual animal/commodity event, and to display image events.If used to view a new event created against the Active Animal, which isthe animal currently being processed, it will allow for the event to bealtered or deleted.

Aliases 426 allows aliases to be created for specific Events orRegimens. An alias can be a RFID or barcode value, such as those of awork cards, or may be any combination of user- or system-defined word,phrase, or number. Before events are created, or identification devicesprocessed, the information is analyzed against the event aliases definedin the system to determine if they represent alternative events thatshould be applied to an animal. Numerous configurations can be createdfor each list of Event Aliases, and their real event types and details.

AnimalControls 428 is an internal ActiveX control that provides eventdata for individual animals. EventValidation 429 is used to check eventdata.

Referring now to FIG. 23, the GroupEvents 444 component permits anyevent or one or more regimen to be applied to a group of animals and tocreate individual event transactions for each animal in that group. Thisability to enter data common to many animals greatly simplifies the dataentry process. The component accesses existing groups in the databaseand presents them in drop-down menus for user selection. It alsointegrates the FilterAnimals and WhichAnimals components to provide botheasy-to-use and complex methods of selecting a group of animals. Thecomponent also allows the user to set the date that the assigned eventstook place.

Regimens 442 is an ActiveX tree-view control used to create andmanipulate groups of events that should be applied to an animal. Itallows for the end-user or administrator to create any number ofregimens that contain specific events. Each event can further describeitself by having child events created that attach themselves to it. Oneor more regimens can be selected to be applied to an animal. This allowsfor the specification and organization of events to be created based onthe process that is occurring, such as animals being calved, or animalsbeing received by a feedlot.

Referring now to FIG. 24, Audio 462 is an ActiveX grid control used toconfigure audio feedback for different permutations of Event types andEvent details. It allows for the differentiation between identical eventdetails for different event types, or a method to override the defaultaudio feedback.

The AudioPlayer 464 sub-component provides standardized audio feedbackto the user. It is responsible for providing specific audio feedback forevent type and event detail permutations as configured through Audio orby system defaults. It is also responsible for the “intelligentplayback” of audio strings like numbers such as “one-hundred twenty-one”rather than “one-two-one”.

The LatestEvent 464 component retrieves and stores specific events. Itis used in forms to allow users to decide what event they want displayedand is used in AgInfoChutes to monitor cells in MicroSoft Excelworksheets.

CheckList 468 is an ActiveX control that allows for user- orsystem-specific checklists to be created. It provides consistentchecklist functionality across components. List items can be added,removed, or modified by the end user as needs change.

Label 470 is an ActiveX control that hooks to the GlobalCore to allowfor language-specific or user-configured labels in the components. Alllabels and text items in the components will allow for their values tobe changed dynamically by the end-user. This allows for completelanguage-customization of user interfaces.

ComboBox 706 provides consistent functionality across components byautomatically extracting Event types, details, or other properties asthey currently exist in the events database or as configured through theEventConfiguration component. It also provides pattern matching as theuser types, and search features.

Referring now to FIG. 25, EventTree 481 is an ActiveX tree-view controlthat hooks to an Animal control 428 to display all the eventinformation, in real time, that exists on an animal. It organizes eventsby the dates that they were applied, and by their hierarchicalrelationships with other events. It uses the EventDrillDown component424 to provide a method for drilling-down into the specific eventinformation including images, which allows for modification of the eventduring the working session of an Active Animal.

Referring now to FIG. 26, the Individual Animal Manager (IAM) 482component is the container that incorporates all three core servers 300,the Animal 428, ApplyEvent 422, Regimens 442, EventTree 481, andnumerous AnimalDataItem 484 components for collecting and viewingtransaction-based data. As the data is created by its subcomponents, itis saved to an Animal's record and displayed along with any historicdata. In this embodiment, the data is displayed in a chronologicalformat using the EventTree 481 component, complete with multi-tierparent/child relationships.

Referring again to FIG. 25, AnimalDataItem 484 is an ActiveX controlthat hooks to the EventCore and extracts specific animal data from thetransactional information. It allows the end-user to select specificevent data to be displayed, such as BIRTHDATE, the last weight, or thefirst OWNER for the “Active Animal”, which is the animal that iscurrently being worked. The control allows for VB Script to be used toaggregate or summarize data, such as by calculating “Age in months”using the BIRTHDATE. The AnimalDataItem 484 is a combination ofLatestEvent 464 and Label 470.

The UserEventCollector 486 scans an Events database and extracts all thedistinct Event Types and Event Details that currently exist on theanimals. This information is loaded into the components database andused by all instances of the ComboBox control 706.

EventConfiguration 488 is used in conjunction with the EventValidation429 component to validate existing data and to ensure that system anduser-defined guidelines are being applied to data as they are collected.

BeefLink Enterprise 492 is a combination of data collection componentsthat utilize a LAN or Internet-based network to retrieve and store eventinformation in a client/server environment. This system can use anyOLE-DB or ODBC-compliant database for event information storage,including SQL Server and Oracle. With events stored in a networkedserver, animal information is immediately consolidated and availableacross all feedlot chutes or enterprise business centers.

Share, Switch, Route, Interface (“SSRI”) Components

The SSRI components 500 are summarized in FIG. 27 and discussed belowaccording to selection and query functions 520 which operate ontransactional data; data sharing and re-formatting of datarepresentation 540; email capabilities 570; processing of data 580; andinterfacing to third party software 590.

Referring to FIG. 28, WhichAnimals 522 is a set of ActiveX controls withuser interfaces to provide a means of isolating the animals, if any,that fulfill user- or system-definable criteria. Providing animal orcommodity information to data marts, data mines, and general reportingtools first identifying which subset of animals or commodities in thedata warehouse need to have information extracted. Since there may bemillions of animals or commodities, segregating the data beforemigrating or transforming it enables efficient processing. The resultinggroup of animals or commodities can be fed directly into the WhatData526 components.

WhichAnimalsUI 524 is a user interface that allows the user oradministrator to create, delete, or alter the WhichAnimal items that areused for identifying the criteria for selecting animals. It simplifiesthe process of selecting animals by presenting a checklist ofWhichAnimal criteria.

WhatData 526 is a set of ActiveX controls, with user interfaces, thatprovide a means of extracting specific transactional data for one ormore animals commodities and providing it in a relational format that istypical for spreadsheets, data marts and data mines. The controls canprocess, aggregate, and summarize the transactional data and provideboth atomic and list-oriented data for every type of event, or eventproperty, that is associated with an animal or animal group.

CheckIn 528 is a component used by copy-protection and eventregistration components to gather “411” and billing information fromBeefLink and Pony Express stations. This DLL searches a system for allevents databases, gathers pertinent information, and delivers it to anInternet-based information server.

Referring to FIG. 29, which illustrates data sharing and representationcomponents, the PonyExpressApplication 542 server application acceptsfiles from BeefLink databases, stores the data, and sends it out toother parties that have the authority and interest in getting the data.It encapsulates the ShareDate 578 component for creating proprietaryAGIL files containing update information necessary for each producer. Itautomatically creates these update files, and emails them to theproducer or Pony Express recipient, and allows including or excludingindividual event types from the output file by the entity receiving thedata.

EventImporter 546 is an application used to import relational data, inthe form of one animal per row with animal attributes in each column ofthe row, from any databases and tables. The application will convertrelational data into transaction-based data, allowing event attributessuch as Animal Id, Date/Time, Entity Id, etc. to be extracted from therelational data. In this embodiment, the application is used to importmost packing plant data.

The EventStorageUpdater 548 application utilizes the Schema Sniffer 250to verify the Events database structure, and to modify it if necessary.It will also provide the ability to make a backup of the database.

AgInfoPorts 554 is a user interface to all serial devices used tocollect data with the components. It allows for connecting any number ofserial devices (one for each port), all with unique filtering,validation, device triggers, and min/max values. The user may set aport's serial parameters and view raw data in the port buffer fortrouble-shooting purposes.

ShareData 578 allows users to easily save and move their data. Thefunctions include disk storage and automatic email capabilities, ftp,and a compacted XML file structure. Data that has already been sent istracked and not sent again, providing incremental update files. Eventscan also be included or excluded from being sent with the AGIL file.ShareData incorporates WhichAnimals 522 and FilterAnimals 608 forselecting specific animals.

Referring now to FIG. 30, the AgInfoPort 554 component connects physicalhardware, such as scales 54, thermometers 55, Ultrasound 56, RFIDreaders 30, bar code readers, and other monitoring devices to the deviceserver 330. The component includes device settings 555 including logicaldevice names and default settings for know devices; serial port settings556 including user configurable port assignment and baud rate; serialport monitoring 557 to display data received through a specified portand logging of that data to a file; user configurable devicecommunications 558 including data to configure the device and to triggerthe device to send information; user configurable data filtering 559 fornoise elimination, string matching, and data stripping; and datavalidation 560 to specify ranges or lists of values for filtered dataand to create indicators of data stability. The component provides agraphical display showing COM port status, current data, and auditinginformation.

Referring now to FIG. 31, PEProcessing 572 automatically searches emailattachments and extracts the entity information such as sender,recipient, time sent, time received, and attachments, and prepares itfor the ETL Engine 630. The data is converted to transaction-basedevents as well as a user-specific data mart.

SendMailControl 576 bundles email messages into a specific format suchas subject field, message text, sender, etc. and ensure properformatting for email-based disconnected networking solutions whereautomated message processing is desired.

Referring now to FIG. 32, ShrinkCalculator 582 is an example of aprocessing component. This application runs simultaneously with theAnimal Manager and other real-time components. During the day, animalsare losing water weight as they wait, under stress, to be processed. Theresult is a weight that is lower than what it should be. This shrink canbe represented as a percentage, with respect to time, of the totalanimal's weight. The ShrinkCalculator component calculates this shrink,and creates an adjusted weight event that describes the animal's trueweight, as if shrink not been a factor. This adjustment can be used inconjunction with AverageDailyGain 722 and WeekToShip 720 to provide moreaccurate finishing weights and information.

The IncomingPriceCalculator 490 component is typically used atchute-side to calculate incoming animal prices by comparing currentweight with a base weight, base price, and value slide.

AgInfoChutes 550 is a real-time extension of the AgInfoSheetstechnology. WhatData items are used to populate Excel™ spreadsheets inreal-time as animals are processed. The component allows for complextemplates to be created with Microsoft Excel that extract Active Animalinformation and notifications from the Event Core. Information can beautomatically used by charts, graphs, equations, macros, and VBAfunctions. In this embodiment, AgInfoChutes has two modes: Single-Animaland Multiple-Animals. Single-Animal mode refreshes the spreadsheet foreach animal as it is processed, allowing for operation similar to theIndividual Animal Manager. Multiple-Animals operation streams in a rowof data for each animal processed, inserting rows for formulas, graphs,charts, and macros as necessary. Embedding AnimalDataItem intoworksheets allows for new events to be created by the worksheets.

AgInfoConvertUltrasound 552 is a specific component written to convertmetric units for ultrasound measurements into English units. Thecomponent establishes a connected with the AgInfoEventCore and monitorsfor any ultrasound events, which it modifies.

EventSort 620 establishes a connection to the EventCore and allows theuser to trap for specific event types and values as they are beingcreated against an animal. Any number of events and values, includingranges of values, can be trapped, and specific audio feedback can bespecified for each. Events may be created in response to this feedbackfrom the Event Core. This component supports fully customizable decisionsupport systems that operate in real-time.

SequenceEditor 622 allows the user or system administrator to configureautomated sequences to be used for event data during animal processing.When an event requests a sequence be used, a user-defined prefix,suffix, and numeric value are concatenated to produce an alphanumericvalue. The numeric value is then incremented by a user-specified amount.Any number of sequences can be created and configured in this manner.

IPrinters 624 runs concurrently with the Animal Manager or Group Eventsto establish a connection to the Event Core to monitor for PRINTER orVISUALID events being created. When these events are created, a barcodelabel for the Animal Id and Visual Id is printed on a label printer.

Processing controls including WeektoShip 720 and AverageDailyGain 722establish a connection to the Event Core and monitor weight events thatare being recorded against an animal. They run simultaneously with theAnimal Manager to provide value-added data gathered during animalprocessing. WeektoShip draws on historic data such as sex and previousweight, and current data such as target weight and current weight, tocalculate the week of the year the animal is to be shipped orslaughtered. The result is displayed and spoken back to the user in realtime as well as written to the database. AverageDailyGain calculates ananimal's gain over the last period for weights collected. It displaysthe gain, speaks it back, and writes it to the database, if desired, andmay graph the history of each animal's weight as the animal is scanned.

Referring now to FIG. 33, interfaces to third party software isaccomplished by both general components and custom interface components592 that are developed for providing specific post-processing fileformats of the third party software.

Importers 594 is an ActiveX control used to extract information fromfixed-width files into an Excel spreadsheet. Data location within thefile is specified in various spreadsheet cells, and the component isresponsible for extracting the data from the file and populating thosecells.

The Share, Switch, Route, Interface (“SSRI”) components are examples ofa data routing layer 664 to the information backbone 606 as described inthe INFORMATION BACKBONE WITH LAYERED PROTOCOLS AND SERVICES exampleabove and as described in FIG. 62.

Extract, Transform, Load (“ETL”) Components

FIG. 34 summarizes the ETL components. EventManager 602 archives animalsbased on events and allows for electronic id tag reuse and scrubs databased upon user or system definable criteria. The EventManager 602component is an example of an Archive and Change Management layer 667 tothe information backbone 606 as described in the INFORMATION BACKBONEWITH LAYERED PROTOCOLS AND SERVICES example above and as described inFIG. 62.

Animal 604 is used to bulk-load all Events for a specific animal. Eventsare loaded directly from the transactional database structure andorganized into a sorted tree structure collection as illustrated in FIG.61. In this example, specific weight event properties are quicklyretrievable according to the date of a weight. The control providesstandardized methods for extracting specific animal data for businessprocessing, aggregation or summarization. Pony Express RelayDatabase™606 identifies the ownership of animal data based on the eventproperties of the events that exist in the data warehouse. In thisembodiment, data ownership is defined as any data that exists on ananimal that had events applied to it by the specific owner in question.The component will also extract, compress, and encrypt the specificanimal data so that it can be propagated to other systems via disk ornetwork connections such as email, web, LAN, or WAN. This is commonlyreferred to as an AGIL file. A version of the component utilizes anyOLE-DB or ODBC-compliant database, including SQL Server and Oracle.

FilterAnimals 608 is a control, similar to WhichAnimals, but provides amore simplified method for the user to select groups of animals based onspecific event values. A combination of up to five of any event, andvalues for each of those events, can be selected by the user in order tocapture the appropriate animals.

Scooper 610 is a set of components that can be used to share databaseinformation between two or more databases or systems. The componentsallow applications to access a database and to isolate specificinformation from one or more tables. This information is extracted,compressed, and encrypted so that it can be propagated to otherdatabases/systems via disk or network such as web, email, LAN, or WAN.These files, called AGILPS files, are then decrypted, decompressed, andimported into a target database. Scooper differs from Pony Express RelayDatabase™ in that it is focused on general component information, ratherthan event information.

TransferEvents 612 loads data into the target Events database from asource database or AGIL file created by ShareData or AgInfoPonyExpressthat is received by another user or by PERD. By double-clicking on anAGIL file, this application automatically starts, checks to ensure theEvents database is properly configured, and imports the data into thedatabase. TransferEvents 612 loads data into the target Events databasefrom a source database or AGIL file created by ShareData orAgInfoPonyExpress that is received by another user or by PERD. Bydouble-clicking on an AGIL file, this application automatically starts,checks to ensure the Events database is properly configured, and importsthe data into the database.

TableExporter 614 uses the Scooper 610 to allow the user to selectcomponent information stored in a database to share with another system.The information from each desired component table is extracted,compressed, and encrypted so that it can be propagated to otherdatabases/systems via disk or network (web, email, LAN, WAN, etc). Theoutput is a proprietary AGILPS file.

TableImporter 616 loads the data found in an AGILPS file created by theTable Exporter into the components database. These files are decrypted,decompressed, and imported using this product. This product allows fordefault information, specific to a target market, to be configured,exported via the Table Exporter, and propagated across multiple targetmachines. The Table Importer also supports a “silent mode” which can beused by an installation application or CD to load default componentinformation specific to that target machine.

Custom interface components 628 provide specific interfaces to customersystems.

AgInfoETL 630 is an extraction, transformation, and loading server thatcontinually monitors the system for carcass information that needs to beprocessed. Information that is received, via email, by the PEProcessingengine is placed within a processing queue monitored by an AgInfoETLservice. Information is extracted from the queue, transformed intoEvents and CISData, then loaded into the carcass data mart, theAgInfoSheets server, and the Pony Express system. Configuration of theserver queue and monitoring settings allows the component to be scaledinto a multiple server environment for distributed processing. Log filesfor each transformation attempt are created and stored to an FTP server.

ETLObjects 632 is a set of objects used for data transformation for ISFF(Industry Standard File Format), and customer output files into CISDataand Events.

EventMaintenance 634 modifies and scrubs data in a CISData mart and PonyExpress server. The component is used to create data validation andmodification rules on the data contained within the mart. Each type ofevent can be assigned default values, as well as locating and correctingerrors in existing data.

Report & Analyze Data Components

FIG. 35 summarizes the report and analyze components 700.UpdateFileReport 702 is a Dynamic-HTML engine that creates an HTMLreport that describes and analyzes the event data found in a filecreated by Pony Express Relay Database™. Each report is integrated withthe Individual Animal Manager for individual animal drill-down; and withthe generate reports utility of AgInfoSheets for group animaldrill-down. This component allows large producers, or data distributioncenters, to report on the information being received, and to process theinformation accordingly; such as generating certain reports for theproducer when packing plant data is received.

WhereInExcel 704 places WhatData items in a MicroSoft Excel spreadsheettemplate.

WhatDataUI 708 allows for the user or administrator to create, delete,or alter the WhatData items that are used for extracting specifictransactional data. The interface simplifies the process of selectingdata for animals by presenting a checklist of available WhatData items.

AgInfoReports 710 is an Access-based reporting engine that allows forreports based on the last occurrence of specific events to be quicklycreated using Access' reporting features. Canned reports are shippedwith AgInfoReports, and many customizations have been made for specificclients. AgInfoReports supports filtering and sorting operations basedon specific event fields used in each report. Variations of this engineallow for specific fields to be created, and exported as acomma-delimited-file.

AgInfoSheets 712 is a reporting tool that complements AgInfoReports bycombining WhichAnimals, WhatData, and the WhereInExcel components as asingle embedded ActiveX control that resides in an MS-Excel spreadsheet.This allows the user to inject any data from an events database anywhereinto an Excel template. Templates that include summary formulas andcharts can be designed, saved, and deployed. With the click of a button,event-oriented data, dates, etc. fill the spreadsheet. AgInfoSheetsallows transaction-oriented data to be queried and presented in aneasy-to-understand form.

RunReports 714 is the primary front-end for producing AgInfoSheetsreports. It provides a tree-view checklist to select the reports andautomates the process of creating each of those reports. It alsoprovides a front-end method of “overriding” the animals that are used ineach report by providing both FilterAnimals and WhichAnimals componentsfor selecting the animals to use.

RequestReports 716 is a client-side application specifically for a CISdata item 724 that presents available animals by lot, packer, sex,market category, etc. in a concise, user-configurable format beforerequesting AgInfoSheets reports from a Server over the Internet.

Custom reports 718 may be developed for specific customers.

The CISData 724 is a carcass information data mart installed onMicrosoft SQL Server. The Data mart has been standardized for use bymore than one customer. Multiple servers/data marts are currentlyhousing information gathered from customer packing plants.

The CISMeatGrinder 726 component loads dynamic HTML templates withcarcass information. It connects to a CISData mart and extractsinformation based upon user-chosen packing plants, kill dates,producers, and market categories; then constructs final HTML output thatis sent to the end browser. Group data is constructed by analyzing theindividual animal data. The component can be used to create HTML reportsbased upon carcass dentition, fat analysis, carcass weights, and groupcompliance.

CustomerWeb 728 is a secured web-based reporting system used forbenchmarking a customer's carcass information. The component is used byalliance administrators, as well as producers contributingproduct/services to the alliance, and provides group-based reportingthat can drill-down to individual animal information. The componentallows for benchmarking between specific producers, kill dates, andlots; and features a security system that filters content based uponuser login and security level. The component is implemented using ActiveServer Pages, and utilizes a CISData mart specific to the customer'sanimals. The FilterAnimals 608, AgInfoReports 710, and CustomerWeb 728components are examples of a data filtering layer 658 to the informationbackbone 606 as described in the INFORMATION BACKBONE WITH LAYEREDPROTOCOLS AND SERVICES example above and as described in FIG. 62.

BatchRun 730 is a server application that monitors requests forAgInfoSheets reports. The RequestReports application is used by theclient to create a request, which this server component uses to generateand email AgInfoSheets reports. Reports are typically sent to eachproducer, but are also consolidated on an FTP server for allianceadministrators.

LotComparison 734 is an HTML based web service used to extractinformation from a CISData mart. The component extracts, and presents,information specific to a packing plant, one or more producer, a rangeof kill dates, or a specific kill lot. The component accepts userselectable date ranges provided through pop-up calendar controls. Thecomponent is used by the IQBSN project as described in an embodimentbelow.

OwnerComparison 736 is an extension of the LotComparison control thatallows for end-user selection to not only select a kill date range, butalso a specific producer. The component allows for benchmarking betweenproducers.

CustomerMaint 738 is an application used by a data administrator tosearch a CISData mart for information specific to a packer, marketcategory, producer, kill date, lot, or animal sex. The component canthen be used to modify the values for the packer, market category,producer, or animal sex. These modifications are also applied to a PonyExpress server.

WebGFX 740 is a web-based search engine used for finding animals basedupon results from a genetics trial. The component allows for quickdrill-down of individual animals based upon gender, breed, ID, and/ormarbling results, and provides ability to add, remove, and edit animaldata on-line.

CRCS 742 is a web-based product registration system used to trackcustomer information and activate deployed software. The componentsupports third-party licensing of InfoPorts; and requires userregistration for product to function. The component records customerinformation for each installed platform, and supplies activation codesto end-users or support personnel.

WebCustomer 744 is a secured web-based reporting engine thatconsolidates individual carcass information for accounting andbenchmarking purposes. Utilizing a PEProcessing and AgInfoETL server,carcass files delivered from several customer packing plants areautomatically transformed and loaded into a CISData mart. When data isloaded, it is immediately available for on-line reporting. The systemcan drill down based upon packing plant, producer, kill dates, andmarket categories. The component supports what-if comparisons betweenmarket categories.

The CustomerWeb 728, OwnerComparison 736, and WebCustomer 744 componentsare examples of a web exposed data benchmarking layer 661 to theinformation backbone 606 as described in the INFORMATION BACKBONE WITHLAYERED PROTOCOLS AND SERVICES example above and as described in FIG.62. The AnimalDataItem 484, WhatData 526, Animal 604, BatchRun 730, andWebCustomer 744 components are examples of a web exposed dataAggregation, Consolidation layer 668 to the information backbone 606 asdescribed in the INFORMATION BACKBONE WITH LAYERED PROTOCOLS ANDSERVICES example above and as described in FIG. 62. The Report & AnalyzeData components are examples of a web exposed data reporting layer 668to the information backbone 606 as described in the INFORMATION BACKBONEWITH LAYERED PROTOCOLS AND SERVICES example above and as described inFIG. 62

Description of Embodiments Component Based Computer Program Product

In this example, the BEEFLINK™ data collection software is a collectionof components written primarily in VISUAL BASIC™ 6.0 programminglanguage and ACTIVE X™ programming methodologies. Most of the componentsof the computer program product are incorporated into softwarecommercially available under the name BEEFLINK™, produced by AgInfoLinkUSA Inc. of Longmont, Colo. The software is an event-based beef cattledata collection and data management system which is easily adaptable toother livestock species by changing the definition of industry-specificdefault events.

Within the computer program product, an event uniquely identifies thedata to which the event relates. The event identifies the person, placeor thing to which the event applies, as well as any parent, child orsibling relations to other data. The classification type assigned to theevent is also specified, such as the type of data that has been entered.The computer program product also contains auditing functionality thatidentifies the creation of the event transaction. The data is auditedaccording to the date and time of the transaction, the transactioncreation method and the origin of the transaction. Any serializable datais stored in the database, including strings, numeric data, date/timedata, and binary/stream file data.

Referring now to FIG. 36, the functions of the BeefLink software 800include user interface and basic functions 805; data collectionfunctions 810 including managing hardware devices that support automatedentry of animal identification and data associated with that animal 815,validating data 820, translating data 825, applying data to a group 830,and computing data 835 such as calculating average daily weight gain anddetermining the best time for an animal to go to slaughter based ontarget weight; and sharing and reporting data functions 840 includingimporting data 845, sending data to third party applications 850,transferring data from one database to another on the same machine orwithin a network 855, injecting data into a spreadsheet 860, and emailtransfer of data 865. The data collection and sharing and reportingfunctions apply throughout the supply chain illustrated in FIG. 6.

Referring now to FIG. 37, which is a flowchart demonstrating an exampledata collection for cattle, an animal RFID transponder is read using anRFID reader at step 2100. The unique animal code is parsed from thetransponder identification from reader software at step 2200. The uniqueanimal code is uploaded to the host computer at step 2300 and stored inthe computer database at step 2400. At step 2500, the host computerconfirms the receipt of the unique animal code, typically throughheadphones or a speaker in the vicinity of the reader. Default animalevent data that is common to the animals is applied by the host computerat step 2550. Animal event data is input using an RFID Work Card and theRFID reader at step 2600. Measurement data, such as weight are capturedthrough multiple input/output devices at step 2700 and uploaded to ahost computer at step 2800. Data may be maintained on more than onedatabase or on more than one computer. Measurement data receipt isconfirmed at step 2900, typically through a speaker; and the animal datais then stored in the host computer database at step 3000. Authorizationlevels are assigned to the data at step 3100. The user may elect todisplay the history of the animal data at step 3200. The authorizationlevels are in the data permission layer 663 of the information backbone606 as described in the INFORMATION BACKBONE WITH LAYERED PROTOCOLS ANDSERVICES example above and as described in FIG. 62. The user may electto input one or more queries on data associated with a particular animalat step 3300, and the data represented the results of the query aredisplayed at step 3400.

When the data collection software receives an animal unique code andtransaction or event data for an animal, the software server writes theevent to a BEEFLINK database. The event data is also sent to otherapplications such as a third party herd management program. The herdmanagement program can be in the foreground and visible while BEEFLINK™data collection software collects data, or it can sit in the background,simply storing data that BEEFLINK collects. The event server notifiesall applications that are in connected to it, and the notificationoccurs for each event created. The event server sends both synchronousand asynchronous messages to other components before, during, and afterany object creation or modification. It also allows for verification,modification or cancellation of the event.

Referring now to FIG. 38, which is a flow chart illustration of thepreferred methodology implemented by the event server, the softwarevalidates the connection authorization and communication encryption byuser, group and component at step 3500, provides standardized methodsfor creating and modifying events at step 3600; ensuring that events canbe represented by user-configurable language at step 3700; ensures thattransactions are created in a standardized and normalized format thatenables accurate functional processing at step 3800; ensures that eventobjects of each type are created within acceptable values, ranges andformats at step 3900; and at step 4000 sends both synchronous andasynchronous messages to connected components before, during and afterany event object creation or modification. Alternatively, the eventserver may validate connection authorization and communicationencryption by user, group and component at step 3500, provide connectedor disconnected views into subsets of event data at step 4100; abstractthe physical storage methods from the components at step 4200; sendsynchronous and asynchronous messages to connected components before,during and after any event object creation or modification at step 4000,and then allows for verification, modification and/or cancellation ofthe event by connected software at step 4300.

A transfer event component permits the transfer of animal data from onedatabase to another on the same machine or within a network. Referringnow to FIG. 39, the user selects a source database from which the userwould like the events to be transferred at step 4400 and selects thedestination database at step 4500. The user may review the event databeing transferred at step 4600. Information designating that the eventswill be transferred is written to the database, and the transfer isexecuted at step 4800.

The software also provides a component for transferring animal data fromone entity to another. Referring now to FIG. 40, the user specifies theentity to which the animal records are to be transferred at step 4800;and the component determines the number of animals in a group and thenumber of animals to be transferred at step 4900. A new event may beapplied to the animal records showing that records were transferred toone entity from another at step 5000.

The software permits the user to transfer animal data to a networkdatabase, a diskette or CD, or PONY EXPRESS RELAY DATABASE™ (PERD)electronic transfer application, so that the data can be shared. Data istypically transferred by electronic mail to a server database with PERD,and the server database may update the user database by sending the userall data to which the user is entitled. The server database will respondto the user by sending only data that was not previously sent to theuser. Referring now to FIG. 41, at step 5100 the user selects the sourcedatabase for animal data to be transferred.

At step 5150, if a tracking database is used to keep a record of animaldata sent to another database or a PERD application, the user will notneed to select a start date or an end date for the data to betransferred. In that case, a tracking file will be created in thetracking database at step 5160 and may be compressed at step 5170. Thetracking database will allow only unsent data to be created in theupdate file which will be transferred back to the user. At step 5200,the user may specify the start and end dates for unsent animal data tobe transferred back to the user. If a tracking database is being used,default dates will be determined at step 5250.

The transfer is preferably executed by electronic mail as in step 5300.Alternately, the data may be transferred to within a network or toanother storage medium such as a floppy disk. If the data is beingtransferred to a network or a disk, the user does the following: selectsa destination database, a tracking database to keep a record of the datasent, views the number of events to be transferred; and creates a filein which the data will be transferred. When the data is transferred byelectronic mail to a PERD application's server database, the computerprogram product uses an unmatched query method to determine other datato which the user is entitled and shares that data with the user. Workperformed at the server database may be manually executed by a systemadministrator. The information shared with the user is determined by theuser's entity identification number. The user may have an agreement withothers involved in the production/processing cycle to share informationonly on particular animals, or to share information on all animals withanother entity.

At step 5400 the software searches the server database for all animalsfor which the entity using the source database has sent data. At step5500, the software searches the server database for all animal data towhich the entity is entitled according to the entity identificationnumber. The computer program product compares all animal data at theserver database to all data that has not been previously sent to theentity and to which the entity is entitled at step 5600. If the entityhas received all the data to which it is entitled at step 5700, then theuser is not sent any data and the component effectively ends its work.If the user is entitled to additional data, then the server or systemadministrator selects the user database for transferring thisinformation at step 5800. A file is created for transferring the data atstep 5900, and the file may be compressed. The unsent data istransferred to the user via electronic mail at step 6000, and the filetransfer procedure ends at step 6050.

Referring now to FIG. 42, at step 6100 the user may select one or morehardware devices including multiple RFID readers, electronic scales,digital thermometers, and ultra sound equipment, as well as databuffering and monitoring devices. The user may configure the hardwaredevice at step 6200 by selecting settings for communicating with thehardware device such as to initialize the device, to open or close thedevice, or to trigger the device to send information. User-configurablefilters are applied to incoming data in order to eliminate noise or baddata caused by interference or device inaccuracies; to allow forsubstring matching that identifies acceptable input; to allow forcapturing only specific data from the serial port; or to allowextraneous data such as prefixes, suffixes, or substrings to be strippedfrom final output. Data validation may be specified such that filtereddata is has acceptable values, ranges, limits and timing. The datavalidation permits specification of a range or list of values forfiltered data; and creation of “stable indicators”, ensuring thatincoming data conforms to the range of value, or is the same value, overa specified period of time. At step 6300, the user may select hardwareproperties by selecting the port number, baud rate, parity, stop bitsand flow control at step 6800. Since there are a number of differentdevice manufacturers, the user may set acceptable input criteria toensure only accurate data strings are accepted.

Regimens permit the user to create multiple events that will be appliedto all the animals processed within a given period. With cattle, thatperiod is typically a morning or a day. Regimens allow the user to savea set of events that may be are used repeatedly for a particular grouptype. For instance, steers of a certain age might be worked identically,therefore the user would be collecting the same data.

Setting up a new regimen is a simple process. A new regimen folder willbe created and the user preferably names the new regimen something thatis easy to recognize. Referring now to FIG. 43, which is a flow chartfor defining a regimen, at step 6400 the user selects the data to beapplied to the group, and specifies the group at step 6500. Where theregimen has already been created, the user has the option of addingchild events to the data at step 6600. For instance, “Dose” may be achild event of a “Vaccinate” event to identify what dose was given of aparticular vaccine. At step 6700, the regimen may be edited such asadding one or more event to the regimen; adding child events; changingevent details through a drop-down menu, such as change of vaccinedosage; or deleting one or more events or child events. The user regimenapplication is executed at step 6800.

The computer program also enables the user to apply individual events toan entire group of animal records, and to apply a regimen to an entiregroup of animal records. Referring now to FIG. 44, a group is selectedat step 6900. The data to be applied to the group is selected at step7000, and the group data is applied at step 7100.

The computer program product supports standardized core events, andallows the user the flexibility to use local or language terminologywhen applying events to an animal's record. The core events do notchange, but the user may rename them for local use. Referring now toFIG. 45, for example, there is a stored core event at step 7200 which isdisplayed with its core event name such as “MetalTag” at step 7300. Atstep 7400, the user may elect to rename the event, and at step 7500, mayrename the event “Bangs Tag” in Montana, or “Caravana” in Mexico. Oncethe user designates a new name, the name is stored at step 7600, and theuser will always see the local name displayed at step 7700 for theevent. At the main database, however, the event is still stored as thecore event, MetalTag, and if no local name has been specified, the coreevent name will be displayed at step 7800. A second user, with differentlocal names can access the event data and have it displayed with hisdesignated local event names. This feature allows data to be normalizedaround the world, and a user can translate events to a new language in ashort period of time. This process applies to both events and eventdetails.

Referring now to FIGS. 46 and 47, the user may predict how long it willtake an animal to reach a target weight for slaughter based on theaverage weight gain per day. The daily gain component determines theaverage weight gain of an animal between the specified dates set by theuser, or if nothing is set, from the last weight event. The ability ofthe user to select the date range of the weight events allows for longerperiods to determine the average daily gain. The user can use thisfunction in conjunction with the week of slaughter component todetermine when the animal will be ready for the packer, or to simplygauge the progress of the animal.

Referring now to FIG. 46, at step 7900 the user is given the option ofspecifying both a start and an end date for average daily gaincomputation, and those dates may be input at step 8000. If both datesare specified, the last weight event nearest to the end date that occursbetween the dates will be used. If there is no weight event that fallsbetween the specified dates, then the first weight event that occursfollowing the end date will be used. Alternately at steps 8200 or 8500,the user may specify only a start or end date, and default dates will beset at steps 8300 and 8600. If no dates are specified, both defaultdates will be set at step 8800. Average daily gain is computed at step8800. External speakers or another output device typically allow theuser to hear the average daily gain when displayed, particularly if theuser does not have a computer on the chute-side. The animal's entireweight history is displayed at step 8900. The user has the option ofallocating the average daily gain as an event at step 9000.

The software contains a component for determining the best time for ananimal to go to slaughter based on a target weight. Since the targetweek is stored in each animal's record, an inventory-type report caneasily be generated, showing the number of animals expected to be readyfor each week. “Default target weights” are desired weights for ananimal at time of slaughter based on the sex of the animal. A defaulttarget weight will be used for setting the target weight for an animalunless a target weight is specified for individual animals.

Referring now to FIG. 47, the user is given the option of specifying atarget weight at step 9100. The user may enter this target weight bykeying it in as one of the predefined events at step 9200. This functioncan be used in several ways. If all the animals being worked will beassigned target weights individually, the predefined event for targetweight can be set as part of a regimen. If the user wishes to enter thetarget weight event individually for each animal, but only wants to use4 or 5 choices for target weights, then the predefined target weightevent and the various details can be assigned to a work card. If theuser does not wish to specify a target weight at step 9100, then adefault target weight is set for the animal at step 9300. The week ofslaughter is computed at step 9400. The user may record as an event thebest time for an animal to go to slaughter at step 9500. The user maygenerate reports for animals ready for slaughter each week at step 9600.

Referring now to FIG. 48, the software supports data checking and theadjustment of the databases to fit the data. The user has the option ofcreating data tables at step 9700 if they do not exist; enlarging fieldor column sizes at step 9900 if necessary; changing field or columnproperties at step 10,100 if necessary; and changing field or columntypes at step 10,300 if possible. These modifications are executed atsteps 9800, 10,000, 10,200 and step 10,400 respectively. The softwaremodifies and enhances database schemas to ensure that data can be storedcorrectly; allows components to be distributed without dependentdatabases or tables; dynamically creates persistent storage space.

For applications that are not able to connect to the computer programproduct in real time, a utility helps import data after collection. Thedata import can be used to import a variety of data types into computerprogram product's database. It allows the user to add specific data likedates and entity identification codes while turning typical columnardata files into data that can be used with a transaction-style database.Imported data is modified such that it can be used with atransaction-type database.

Referring now to FIG. 49, a first data injector component includesprogram code for injecting the data into a spreadsheet for presentation,storage, and reporting. This tool may be used to bring together groupdata from feedlot management programs along with carcass data frompacking plants and inject the results into a proprietary feedlotcloseout spreadsheet. The program begins by searching electronic mailfor files of a particular type at step 10,600 and displaying some of thedata for validation at step 10,700. The data is then injected into thespreadsheet itself at step 10,800. As data flows into the spreadsheets,the data is mapped to specific worksheets and cells within thespreadsheet at step 10,900.

Referring now to FIG. 50, a user may access the data in BEEFLINK datacollection software and inject it into a MICROSOFT EXCEL™ spreadsheet.The reporting tool is in the form of an ActiveX control and is siteddirectly in the spreadsheet. The user selects the data to be displayedat step 11,000, and places the label for that data in a spreadsheetcolumn at step 11,100. The user can also use any mathematical functionsalready available in Excel such as sum or average, to performcalculations on the data at step 11,200. In order to select and filteranimals and data, the user determines which animals will be in thereport by selecting those animals at step 11,300. The animals can beselected in any combination in which the user is interested, such as allAngus steers that were slaughtered in the last six months with an originof a particular ranch. After the animals have been selected, the userdecides what data will be displayed, such as the weaning weight,feedlot-out weight, carcass weight, carcass grade and yield and implanthistory. The user selects the data desired for reporting at step 11,400.Once the data is selected, the report is run and saved with a particularname at step 11,500 and can be used at any time with the current data inthe database.

This architecture permits the user to adopt an appropriate technologyfor data collection ranging from the manual collection of the CattleCard™ to Personal digital assistant (PDA) devices, to laptop computers,to enterprise fully on-line computing. The user may adopt thick or thinclient solutions as appropriate, so that the system allows real-timecomputation for on the spot-decision making where appropriate. Thepassive data collection reduces training requirements and data errors.Distributed, cascading databases address producer privacy concerns andscaling issues, and provide a mechanism for consolidation, filtering,and benchmarking of large amounts of data.

The transaction based data structure permits new data elements to becollected by a customer without underlying change of data existingschema. The data schema can be changed at the data mart level, therebyproviding more flexible and more expandable data. Each transaction isdate and time stamped in order to create an inherent audit trail, highersecurity, and a more tamper resistant database. All records aretamper-evident.

The data can move from the transactional to a relational database incases where the relational database is appropriate for some dataprocessing.

The inherent parent-child relationships for each event enable thecreation of many to many relationships within the database. The eventtranslator allows a producer to use familiar nomenclature.

The open system architecture supports and encourages the use of thirdparty software for value added applications and permits BeefLink to beused with minimum disruption. Reusable architectural components permitthe rapid creation of semi-custom solutions. Standard tools such asMicrosoft Excel may be used for data analysis.

Real time web applications may be employed; or near-real-time webreporting reduces infrastructure cost compared to true real-time systemand allows the system to become self-balancing. The system leveragesInternet email by delivering updates to and from the systemautomatically or semi-automatically using an email system.

Top level data coordination via “Agil 411” provides network coordinationthrough a brokering private network links service protocol layer 665 tothe information backbone 606 as described below and as described in FIG.62 while still maintaining data privacy.

The data structure and components permit an easy expansion of the systemto any agricultural commodity; and to rapidly upgrade the applicationsdue to the robustness of the transaction data structure.

Example AgInfoLink.Net System

Referring now to FIGS. 51-58 which are screens from a web-basedinformation system for a beef marketing alliance, shareowners in theIowa Quality Beef Supply Network (IQBSN) may access a web site(http://www.AgInfoLink.net/IQBSN) to obtain secure harvest data throughon-line reporting capabilities. IQBSN is a management tracking divisionof the Iowa Cattlemen's Association. The division offers producersopportunities to learn more about the quality and consistency of thebeef they are producing through the creation of a database which trackscalves from birth to box.

Users visit the site for access to harvest and production data fromtheir cattle marketing. The site provides each password-protected useran overview of harvest lot information including quality grade, yieldgrade, and carcass weight. Ribeye area and backfat measurements areavailable for measured cattle. The data is displayed in an easy to readmatrix format that can be sorted, filtered, and exported to MicrosoftExcel or a herd management program for further analysis. The site alsooffers individual animal reporting that presents IQBSN grid premiums ordiscounts for each animal, allowing producers almost immediate feedbackon individual animal performance. The harvest data is matched with liveanimal production data, and the online system even allows for onlineaddition and editing of production information.

The IQBSN harvest data is calculated on a proprietary IQB grid,negotiated by the Iowa Cattlemen's Association for their members, withExcel Corporation at their Schuyler, Nebr. plant.

The site gives the user the ability to compare a selected harvest lot tothe rest of his cattle harvested within a user-specified date range. Theharvest lot may also be compared to the cattle from all owners within auser-specified date range. Users benefit from the ability to benchmarktheir cattle performance to other cattle they have marketed and tocattle marketed by other IQBSN shareowners. System Administrators havethe added ability to compare selected harvest lots or cattle within aspecified date range for any owner.

Referring now to FIG. 51, after logging on, users enter a “Select KillLot” for selecting animal lots for reporting. The user may select thedate range of kill dates, and then click the search button. A list oflots that were killed between those dates will be displayed in reversechronological order. Alternately, a single lot report may be directlyaccessed. A consolidated view of all lot reports is also available. Amember is restricted from accessing lots other than those associatedwith his member number, while an administrator has the added ability toselect kill lots for any of the members.

Referring now to FIG. 52, a lot overview page includes headerinformation for the specific lot including Harvest Date, Owner, Member#, Lot #, Total Animals, Packing Plant, Base Price, Cost spread, etc.;distribution tables for the Hot Carcass Weight, REA Adjustment, FatThickness, and a Carcass Matrix that describes where all the animalsfell along the pay grid. In this example, Lot #2630 comprised 95 animalsowned by J. Wilhett Farms.

Referring now to FIG. 53, a lot comparison screen permits analysis of aspecific lot against all the owner's lots, as well as all other owners'lots in the data set. The date range for finding specific lots forcomparison is user-selectable, but defaults to the date range selectedin the “Select Kill Lot” screen. The start and end dates can be changed,and the user may select either his member number or “ALL”. Using “ALL”will compare all cattle from all members in the given date range. Thedata includes distributions for Dressing Percentage, Back Fat, Rib EyeArea (REA), REA Adjustment, Hot Carcass weight, % KPH(Kidney/Pelvic/Heart fat), Yield Grade, Carcass Value per hundredweight, Total Value, Premium per head; as well as values for PercentChoice or Better, and Number of Head in the selected lot.

Referring now to FIG. 54, a report may be generated to show informationfor each animal. This report allows members to filter, sort, and editanimal data. This reports not only includes the carcass data, but also16 points of individual live animal data that can be reviewed and/oredited at the member level. Those 16 points include the Visual ID, DamID, Sire ID, Sex, Calving Ease, Birth Date, Birth Weight, WeaningWeight, Age of Dam, Color, Group, Origin, Date Weaned, Feedlot In Date,Feedlot In Weight, and Average Daily Gain. The system has been designedto support any live-animal data collected at the producer, however,these 16 items support the current reporting needs of the IQBSN to trackanimal origin, genetics and production information.

Referring now to FIG. 55, live animal data which was collected by theproducer or feedlot is accessible and the user may manually add liveanimal data by scrolling to the right hand side of the screen, clickingon the “edit row” button, and filling in or editing the cells.

Referring now to FIG. 56, which is an example of the individual animalstable without graphics, the user may click a button to export the datato MicroSoft Excel for further analysis and graphing. The file is savedas a Web Page (*.htm, *.html). MicroSoft Excel is then opened, and thesaved file is opened into Excel where the user can use Excel functionsto sort, filter, graph, etc. the data.

Referring now to FIGS. 57 and 58, which are 2-view and 4-view examplesof a comparison-reporting feature. The 2-view page by default, will showcomparison tables for all cattle, across all owners, broken down intofinancial quarters. The user may select his lots or “ALL”, and mayselect the date range for comparison.

The user may open a report into a new window in order to eliminate thegraphics and provide a larger data viewing area.

Example Value Based Feeder Cattle Procurement System

In this embodiment, individual animals are identified, and attributesincluding breed, size, weight, frame size, and flesh condition arerecorded for each animal. Values are assigned to the attributes, such asa premium of $1.00 per hundred weight for an Angus breed, a base priceof $85.00 per hundred weight for a 600 pound steer, $1.00 premium perhundred weight for a specified vaccination program, or $2.00 per hundredweight premium if the animal has been weaned for at least 45 days. Thesevalues are user-adjustable. A feedlot can access the data fromindividual producers or groups of producers and identify specificanimals that meet its target specifications, and can acquire thosespecific animals. This value-based approach permits the feedlot toacquire specific animals to better meet its particular business goals;and allows the producer to obtain a premium for supplying animals thatprovide more value to his customer.

Example Shared Premium Procurement

In this embodiment, a producer who believes that he is supplying betterthan average quality animals contracts to sell those animals to aproducer for a combination of (a) an average market price immediately;and (b) a share of any premium recognized by that animal upon its sale.As the majority of cattle are now sold on a value grid system, thefeedlot can share risk and reward with the producer. The feedlotoperator is able to acquire better animals at a lower initial price; andthe producer is able to recognize more income from animals that do proveto have additional value to the packer. Individual animal identificationand data collection provide historical data that the feedlot operatorcan evaluate in making a purchase decision; and continued dataacquisition for the animal provides health, feed efficiency, and carcassmerit information that may be used by the feedlot and the producer tobetter identify the performance of individual animals. Those animalsthat demonstrate more efficiency in weight gain, better health, andhigher carcass grades provide better return to the feedlot. As thoseanimals are sold, the producer is able recognize a portion of thepremium over an average carcass. For instance, a producer sells an 750pound calf to the feedlot at the then-current average market price of$85.00 per hundred weight. The feedlot feeds the animals for about 20weeks. The animal is then sold on a grid system and its 750 poundcarcass grades at the upper ⅔ of the Choice grade which represents aprice of $1.25 per pound versus $1.17 per pound for average carcass. Atthis point, the carcass has a value that is $60.00 higher than anaverage carcass. The producer receives a premium of $30.00 due to themore efficient weight gain and the higher carcass value. The feeder hasrecognized additional profit of $30.00 without incurring the risk ofhaving paid a higher price for the animal.

Example Supply Chain Management

In this embodiment, groups such as marketing alliances have contractedwith processors to supply a given quantity of a product such as beefcattle meeting specified criteria. For instance, a packer is to besupplied 1,000 cattle per week with a finished weight of 1,250 poundsand meeting certain quality characteristics. One challenge to this typeof marketing alliance is that it takes 16 months from birth for a beefanimal to reach the packer. The alliance uses individual animalidentification and the BeefLink data collection and data sharing methodsto have a visibility to prospective animals over the next 12 months. Thealliance can plan the delivery of specific animals to a feedlot in orderto meet this schedule, and can make decisions regarding the actual endpoint; or of accelerating or delaying the weight gain, and thereforedelivery data, of specific animals.

Example Financing

A traditional livestock lender typically will finance 70% of the valueof a beef calve. The owner or operator is responsible for providing theother 30%. These values are based on historical practices and averagecattle values and risk. This cost of financing can be lowered byproviding the traditional lenders with a lower risk, and by providingtools that permit other lenders to provide funding. A lender can reducerisk by identifying and tracking individual animals, and by knowingthose animals' history and performance. A risk-adjusted financing of85-90% of a calf can reduce ownership costs by $50.00 to $120.00. Therisk can be shared by performing market analysis throughout theproduction cycle. Generally, the animals will become more valuable overtime, but the risk of market downturns and individual animal loss can beborne by the producer more economically by adjusting the “margin call”in these circumstances than by self financing the 30%.

Some of the lender risk is due to a very small number of producersmisrepresenting their collateral. Individual animal identificationpermits a virtual national lien registry of individual animals so thatthey cannot fraudulently be used as collateral in multiple loans.

Example Swine

Another example of livestock data collection is the use of handhelddevices, work cards, and BeefLink to capture swine data including numberof pigs farrowed, pig loss, and dam data.

Example Hand Held Device Data Collection

In this embodiment a hand held device such as the Pocket Tracker™System, provided by InfoClip LLC, has an RFID reader and a small displayscreen. The device is used to read an animal or work card RFIDtransponder remote from a host computer. After data collection,typically from several animals the hand held device is synchronized witha host computer running the BeefLink program.

Example Email Update of Carcass Information

Referring now to FIG. 8 which is a flowchart of an email file updatemethod, data files are prepared at one or more packing plant 132 a-132 cto provide carcass data and other information which can be related toindividual animals. The carcass data is attached as a file to an email136 from a customer computer 133 to a host computer's 135 POP Server134. The PEProcessing component 572 automatically searches emailattachments and extracts the entity information such as sender,recipient, time sent, time received, and attachments, and prepares itfor the ETL Engine 630. The information in the packer files is convertedto transactional format if necessary. The customer can request reportsthrough the Report Engine 716. The reports typically marry carcass datato individual animal data and present the data to the customer in anExcel pivot table. These updates and reports are typically performeddaily.

Example Tracing Food Products

Referring again to FIG. 7, one or more food tracking databases 123 isextracted from a plurality of distributed PERD transaction databases 118in order to provide a history of a food item through multiple ownershipand multiple product forms, from live animal to carcass to disassemblyin a packing plant to individual meat products. These food trackingdatabases provide a basis for auditing the ability of a supplier totrack food products forward or backward, and to quickly and efficientlyrecall specific products when necessary.

The data was collected at step 116 with BeefLink software 20 and thirdparty software from entities through the supply chain including cow/calfoperations 83, auction sales 101, stockers 84, feeders 85, packers 86,retailers and consumers 98. This data collection is accomplished withouta loss of historical data through the supply chain, without the expenseand errors associated with re-entering the data at various points in thesupply chain. The data is collected in, or converted to, a transactionalformat as described below.

The transactional database and the audit features of the data structurespermit an analysis of the integrity of the data and to determine whenand if any alteration was made to the data. The transactional nature ofthe data also provides an audit trail and chronology of events. Thearchitecture is robust and is quickly adaptable to products at any pointin a livestock supply chain. Data capture can begin immediately withoutwaiting for business rules and database design to be developed.

In the case of red meats, some data on live animals will be available ata packer upon the animals' arrival. As events occur during the packer'sslaughter, quartering, batching, de-boning, fabrication, packaging, andshipping operations, that information is entered and stored. Assubsequent events occur such as batching of products, and movement ofproducts, those events can be entered and stored. The robust methods ofstoring and extracting that data into meaningful information comprisesthe functionality of a food tracing system and other applications.

After the data is collected it is pushed at step 117 to PERD transactiondatabases 118, where it is available at the next stage for sharing withprevious and subsequent owners. It can be sent automatically via acompacted email or electronic transfer. If the data collector is online, the data can flow from a remote database in real time. Ifnecessary, the data can also move physically, such as mailing abar-coded card containing event data as in the case of the CattleCard14; sending information along with the animal as in the case of theEuropean passport system; or sending the information in portable dataformat such as bar code or RFID.

The original or raw data is stored in a transactional, event-oriented,format including Date/Time stamps for the actual event, and optionallyfor the time that the event was entered into a database. The databasenot typically a central database structure, large scale data sets areboth logically and physically distributed, and organizations that aregeographically distributed need a decentralized approach to reportingand decision support.

The data is extracted from the raw transactional databases, transformedinto the type of data storage structure necessary for a particularapplication, and loaded into use-specific structures called data martsat step 120. Third party databases are typically accessed in thegeneration of the data as described in FIG. 6, or in the creation ofdata marts at step 120.

Data Structures

The data is collected, transferred, and stored in a transactional,event-oriented, row-oriented structure with very few columns. Unlikerelational databases, there are no tables to relate to each other. Thetypical relational database structure places dynamic events that occuron the animal in their own tables. There are often tables of datarelated n complicated ways.

The transactional structure eliminates the need for defining relationalstructures between the tables by allowing all events to be entered astransactions, with event names replacing table names (i.e. Treatmentbecomes an event instead of a table). The transactional structure isentirely extensible, so that whenever a new type of data needs to beadded, the user simply starts collecting an Event with that field's nameand the data collected is stored as the Event Detail for that Event.

Referring now to FIG. 59, which is an illustration of a data structure,each item in the list represents a column in the table. The data tablescomprise a set of rows, where each row is of this data structure. Onecolumn in the data table is called an “Event” and is in combination witha second column called an “Event Detail”. The values in the Event columnreplace the columns of a typical database table so that values such asBreed, Batch #, Location, Vaccination, Carcass ID, Birth date, etc. arenow simply values stored in the Event column. The values in the EventDetail column replace the values that would be in each of the manycolumns of a columnar database.

The event and event detail together form attributes of live animals,carcasses, or other forms in the supply chain.

The data structure also included a unique identifier such as Animal IDas the item about which information is collected. This can be anyitem—an animal, a carcass, a batch, a primal, a sub-primal, etc.,depending on what item is having information added to it.

Every event in the table has a globally Unique Event ID associated withit so that no matter where that row of data ends up, it is uniquelyidentified. In order to connect two or more events, the “child” eventstores the Unique Event ID of its “parent” in the Parent ID column. Thisallows relational features within a single-table architecture.

The Date/Time stamp column is used to insert the exact timing of thecollection of an event and detail. This acts as both a chronology and anaudit trail of the timing and sequence of all event entries. The EntityID is the field that identifies the entity which posted each event. Therecord entry method (REM) identifies how an event entered the system,such as keyed in, scanned in, put in as a regimen, as a group, etc. TheDate/Time stamp, entity, and record entry method elements of the datastructure provide an audit capability and support a data integrity layer656 and a event tamper evident layer 655 to the information backbone 606as described in the INFORMATION BACKBONE WITH LAYERED PROTOCOLS ANDSERVICES example above and as described in FIG. 62.

The Security Level is typically used to restrict access to portions ofthe data.

The transactional structure is an extremely flexible and extensiblearchitecture. Database architects do not have to plan for, or even knowabout, each field that will be in a database. Nor do they need toconstruct the relational tables and links that are required in arelational database structure.

Data Entry and Retrieval

Referring now to FIG. 60 which is an example of the linking of eventtables, to link the tables together, the Event Detail of the previousdata table is linked to the item ID of the next table.

As an example of the linking of event tables through the supply chain, alive animal is slaughtered, and its carcass is converted in a batch andthen to primals. A live animal is uniquely identified with an Animal ID.This Animal ID is common through changes of ownership of the liveanimal. Changes in ownership of the live animal are recorded as eventsfor both the seller and the buyer where an event detail identifies thebuyer and the seller, respectively. In this manner, the ownership of thelive animal can be traced, and events and event details from every ownercan be accrued.

This same type of logging occurs when the form of the livestock itemchanges such as at slaughter where a live animal is converted to acarcass. In this case, the identification changes, but a unique carcassid can be linked to a unique animal ID by providing the carcass ID as anevent detail in the feedlot's Animal Events table as illustrated in FIG.60. An event, CID, has an associated event detail of the unique carcassid.

As the carcass is disassembled in a packing plant or subsequentprocessing plant, similar Batch IDs and Primal Ids can be linked throughevent details of the previous owner or processing stage, therebyenabling access, in either direction, of all data related to each of theentities associated with each form of the livestock.

For efficiency, the “411” data warehouse 119 is typically maintained toidentify each entity associated with a particular animal, carcass, etc.

This structure permits a flexible and extensible method for trackinglivestock and other agricultural items through multiple owners andmultiple forms, including assembly or disassembly.

The transactional table structure is identical regardless of the itemfor which data is being entered.

Data entry is typically performed at various disconnected sites intoseparate databases. However, since the data is being collected ondifferent items—animals, batches, primals, etc., the transactional tablefor all animals, a separate table for all batches, another for allprimals, etc. can be located in one central database or in disconnectedstructures that link the tables. Once data is received into its correcttable, the system can be queried to perform trackbacks and trace forwardfunctions. Additionally, the data can be extracted into specific datamarts at step 120 for labeling and lookup operations.

The structure is extensible to further processing; for instance, theprimals could be split into sub-primals, and the transactional structureused to link back to PID.

Once the relationships between the event tables are established, thedata from all of the tables can be queried, displayed, looked up, moved,etc.

When a Batch ID number is queried, the Animal IDs, Carcass IDs, and thePrimal IDs that make up that batch can be identified, and dataassociated with those other entities can be accessed. Similarly, thequery of any of the other entities will also provide limited access todata for the other entities. These same results can come in the form ofa report or as data used to describe or list the makeup of a batch forlabeling and/or verification reasons.

Therefore, an animal may be traced forward to see where the primals forthat animal have been sent; or products such as primals may be traced toa batch and individual animals within the batch. Even if individualcarcass information is lost in a patch process, the list of animals thatmake up the batch are known. Alternately, a batch size of one can beused to provide a certain linkage to a specific carcass and animal.

The event structure contains full auditability of each atomic data item.

The Events of this structure standardize the actual data into an atomiclevel: an Event is an attribute with relationships to rows and othercolumns. In this data sharing environment, the structure of the tableswill always the same, as well as the structure of each row.

With this structure, data can be collected and shared, so that businessrules can be applied once they are discovered.

The advantages of the architecture include: the ability of each producerin the supply chain to select an appropriate data collection technologysuch as manual collection, hand held devices, laptop computer, or online collection; the use of passive data collection to reduce keyboardentry; the selection of appropriate thin client or thick client solutionat any point in the supply chain; the use of distributed, cascadingdatabases which, support various security levels, to address producerprivacy concerns and provide scaling while still providing mechanismsfor consolidation, filtering, and benchmarking; the use of a transactionbased data structure to permit new data elements to be collected withoutchanging the underlying data schemes and to support appropriate dataschemes at the data mart level; inherent parent-child relationship foreach event, thereby supporting many-to-many relationships; an eventtranslator to permit each producer to use nomenclature familiar to him;underlying software cores to providing rapid interfacing to third-partysolutions; a Date-time stamped audit trail for all transactions; andtamper-evidence records, for reducing post-hoc fraud; producer dataownership and routing to reduce resistance to imputing data into thesystem; the ability to support transaction pricing to lower entry cost;an open systems architecture to support third party applications; arugged hardware and software system for real world operations; reusablecomponents to support fast implementation of semi-custom solutions;leveraging of familiar standard uses spreadsheet tools for dataanalysis; real-time web or near real-time reporting to reduceinfrastructure cost relative to true real-time systems and to support anappropriate level of computing at each point in the supply chain; toplevel data coordination through the “All” data warehouse to providenetwork coordination which maintaining data privacy; and support onInternet email as a familiar data transfer mechanism.

Example Source Verification of Feeds

One aspect of source verification of livestock is the ability todetermine whether a particular animal was fed genetically modifiedgrain; feed made from partially from animal protein components such asthat associated with BSE; and whether an animals diet has been limitedto organic products. This type of analysis permits a vendor to confirmcompliance with regulatory restrictions, and it permits the vendor tocertify product as being GM-free or organic.

The BeefLink system permits feeding sessions to be events and permitsthe identification of particular feed lots. These events are similar tothe way that vaccination events can reference specific lot numbers ofvaccine. In the vaccine example, overall pharmaceutical usage can becompared to reported event vaccinations. In the feed example, specificlots of grain or other feed can be identified so that source and natureof the feed can be tracked; and the reported usage of the feed can becompared to supply records.

In a manner similar to that described in the above embodiment, specificanimals can be linked with events and event details to specific feedidentification can be tracked backward and forward in both the feedsupply chain and the animal supply chain. In one application of thisexample, contaminated feed can be linked to specific animals or groupsof animals, or animal feeds can be source verified to be organic ornon-genetically modified.

Example Food Information Highway™

The FOOD INFORMATION HIGHWAY™ of AgInfoLink Global Inc. is an example ofan information backbone. In this example, the information backbone is aglobal transaction-based system that enables value traceability andregulatory traceability for food supply products. Agribusinesses cancollect, transfer, selectively share, extract, load, transform, andreport on individual units of production throughout the food supplychain.

The FOOD INFORMATION HIGHWAY™ uses data collection tools such as theBeefLink™ system as described in THE BEEFLINK™ DATA COLLECTION ANDMANAGEMENT SYSTEM example, TracBac™ system for tracking and reportingfood product information from the processor to the consumer, CattleCard™14 manual enrollment system for collecting individual food unit andgroup information without a computer, and data collection devices suchas the TagTracker™ RFID reader.

Data sharing in the FOOD INFORMATION HIGHWAY™ is provided by the PonyExpress Relay Database™ 606 that facilitates the secure sharing of dataamong groups, alliances, and companies and provides services such asdata-mapping from dissimilar data structures, inter and intra-recorddata integrity, micro-accounting, change management and other services.The backbone and layered services provides for quick, selective, andsecure data transfer among individuals or groups in a data network. Dataon individual food units is moved from one location to another withindecentralized data sharing networks, and previously approved informationmay be shared among different private data networks. The backbone canuse the Internet or an intranet to facilitate secure and fast datamovement.

Data analysis and reporting tools permit detailed reports using datamart technology. Reporting tools include AgInfoReports 710, a flexiblelocal reporting system; AgInfoSheets 712, a stand-alone andInternet-accessible local reporting tool; AgInfolink.Net onlineweb-enabled information system such as the Iowa Quality Beef SupplyNetwork (IQBSN) described in the AgInfoLink.Net system example, or anythird party reporting tools.

Example Event Accounting for Microcharges and Microcredits

In this example, an event accounting service layer 660 is provided to aninformation backbone 606 such as the Food Information Highway™.Referring again to FIG. 7, as data from an entity such as cow/calf 83,feeder 85, retail 98, etc. is entered at step 117 into a transactionaldatabase 118, one of the data elements in the data structure is theentity id as shown in FIG. 59. In this example, the entity is the ownerof the data and may authorize which, if any, other entities or relatedthird parties such as consultants, may access the data.

In general, at least during the early stages of creating an informationbackbone, there are two obstacles to collecting that data which may beuseful at other stages in the supply chain. One obstacle isinconvenience—that the desired data collection may be viewed as anuisance or inconvenience by the entity that would be responsible forcollecting the data. The second obstacle is privacy, in that while somedata, such as purchase price, is useful to the collecting entity and toa portion of the other entities in the supply chain, as well as toconsultants or parties associated with the collecting entity; the entitydoes not want to share that information with competitors or some of theother entities in the supply chain.

In this example, the second obstacle is addressed by permitting the datacollecting entity, which owns the data, to specify an authorizationlevel to the data. The authorization level determines which, if any,other entities or related parties may access that data. An example ofthis data permission is the security level data element in the datastructure of FIG. 59. The data permission layer 663, as described in theINFORMATION BACKBONE WITH LAYERED PROTOCOLS AND SERVICES example and inFIG. 62 evaluates the requesting entity's authorization to access thedata, and if access is authorized, proceeds with routing the data tothat entity.

In this example, the event accounting layer addresses the first obstacleof inconvenience by rewarding the data collecting entity for collectingthe data. The event accounting layer keeps track of the source of thedata as identified by the entity ID data element. This entity ID isstored along with the data until the data is reformatted, such as in adata mart 122-129 as illustrated in FIG. 7. In other embodiments, theentity ID is stored in the data marts.

Referring now to FIG. 63, a data collecting/ownership entity 690provides data element 691, such as through extraction from an existingentity software application or from new data collection, at step 117 toan event transaction database 118 in an information backbone 606. Thedata structure may include data elements as shown in FIG. 59 and FIG. 63such as an animal, food item, or other agricultural id 691 a, the event691 e, and event detail 691 f. The data structure may also include anentity ID 691 g which identifies the entity that owns the data, and asecurity level 691 h which specifies restrictions on sharing that datawith other entities.

A data accessing entity 693 a may, if permitted, access that datadirectly from the information backbone. The query is directed through aseries of layered services and protocols such as described in theINFORMATION BACKBONE WITH LAYERED PROTOCOLS AND SERVICES example and inFIG. 62. In this example, those layers include a data permission layer663 to determine if the accessing entity is authorized to receive thedata, a data routing layer 664 for directing the data at 692 a to theaccessing entity, and an event accounting layer 660 which at step 694 cdetermines microcredits 695 a due to the data collecting/ownershipentity 690 for collecting the data, and microcharges 695 b due from theaccessing entity 693 a for accessing the data. The event accountinglayer then aggregates 696 the costs and sends an aggregated invoice tothe user of the information, and sends the received monies, afterdeducting a transaction fee to be paid to the information highwayservice provider, in an aggregated check to the information provider.These individual charges and credits are typically very small, such ason the order of very small fractional cent per unit of production, so itis desirable to accumulate those credits and charges, and to issue aperiodic statement.

A data accessing entity 693 b or 693 c may also access the data from adata mart such as illustrated by 123 and 128. In this example, the datapermission and routing are determined as before, and the data is routed692 b to data mart 123, and routed 692 c to data mart 128. Microcreditsand microcharges for introducing the data to the data marts aredetermined at 694 a and 694 b respectively. In this case, one or moreaccessing entities may be associated with the data marts, and thecharges are determined by entering the data into the data mart.Alternately, the actual use of data from the data mart may be monitored694 d and charges calculated based upon actual use of the data.

Individual payment credits may be very small, but there may be a largenumber of items, and the incremental cost of collecting that data can bevery small. The data may be extracted along with other data from anexisting entity application program, or the data may be collectedautomatically with tools such as the data collection systems describedin other examples. Once a collecting entity begins collecting theadditional data, that entity has opportunities for process improvementby analyzing that data. While this process improvement opportunity maybe more significant than the fees generated from the data, the fees canprovide a tangible incentive for the collecting entity to implement thepractice of collecting more data.

In this example, the entity entering the information, regardless of thesegment of production, is the owner of the data, and that entity maydetermine with whom information is shared and at what price, if any.Some downstream entities may require free access to certain types ofdata as part of acquisition contract terms. In this case, the value ofthe data may be taken into account in the price of the item.

In the case of the Food Information Highway, there is a value inidentifying the history of a food product, and knowing this history canadd value to the product independent of the information itself. In somecases, it is possible for a supply chain processor or distributor toreceive a higher price for a commodity item that has this type ofdocumented history. In those cases, producers and upstream processorsmay benefit both from being credited with collecting that information,and with being paid higher prices for their items.

1. A computer-implemented method comprising: automatically certifyingusing one or more processors, whether a product satisfies a claim,further comprising: establishing a data collection interface between afirst supply management device and a transaction database, the datacollection interface providing the transaction database with access toidentification data and event data, the identification data uniquelyidentifying the product, and the event data relating to a feedingprocess associated with the product, receiving a product trackingrequest for formatted identification data or event data from a secondsupply management device, and establishing a data conversion interfacebetween the second supply management device, and the identification dataor the event data, the data conversion interface providing the secondsupply management device with access to the identification data and/orthe event data, according to the product tracking request; andoutputting a result of the automatic certification.
 2. The method ofclaim 1, wherein the claim is a genetically modified (GM)-free claim oran organic claim.
 3. The method of claim 1, wherein outputting theresult further comprises displaying whether an animal was fedgenetically modified feed or feed made partial from animal proteincomponents, or whether a diet of the animal was limited to organicproducts.
 4. The method of claim 1, wherein automatically certifyingwhether the product satisfies the claim further comprises automaticallydetermining whether the product satisfies regulatory restrictions. 5.The method of claim 1, wherein automatically certifying whether theproduct satisfies the claim further comprises causing a third party tocertify the product as being genetically modified (GM)-free or organic.6. The method of claim 1, wherein the event data uniquely identifies aparticular feed lot or a feeding session.
 7. The method of claim 1,wherein automatically certifying whether the product satisfies the claimfurther comprises comparing the event data to a supply record.
 8. Themethod of claim 1, wherein automatically certifying whether the productsatisfies the claim further comprises linking contaminated feed tospecific animals or groups of animals.
 9. The method of claim 1, furthercomprising: encrypting and decrypting the event data; and performing anauthentication operation on the second supply management device, whereinthe data conversion interface is established based on successfulperformance of the authentication operation.
 10. A computer programproduct, tangibly embodied in a machine readable storage medium, thecomputer program product comprising stored instructions that, when readby a machine, operate to cause data processing apparatus to:automatically certify using one or more processors, whether a productsatisfies a claim, further comprising: establishing a data collectioninterface between a first supply management device and a transactiondatabase, the data collection interface providing the transactiondatabase with access to identification data and event data, theidentification data uniquely identifying the product, and the event datarelating to a feeding process associated with the product, receiving aproduct tracking request for formatted identification data or event datafrom a second supply management device, and establishing a dataconversion interface between the second supply management device, andthe identification data or the event data, the data conversion interfaceproviding the second supply management device with access to theidentification data and/or the event data, according to the producttracking request; and output a result of the automatic certification.11. The computer program product of claim 10, wherein the claim is agenetically modified (GM)-free claim or an organic claim.
 12. Thecomputer program product of claim 10, wherein outputting the resultfurther comprises displaying whether an animal was fed geneticallymodified feed or feed made partial from animal protein components, orwhether a diet of the animal was limited to organic products.
 13. Thecomputer program product of claim 10, wherein automatically certifyingwhether the product satisfies the claim further comprises automaticallydetermining whether the product satisfies regulatory restrictions. 14.The computer program product of claim 10, wherein automaticallycertifying whether the product satisfies the claim further comprisescausing a third party to certify the product as being geneticallymodified (GM)-free or organic.
 15. The computer program product of claim10, wherein the event data uniquely identifies a particular feed lot ora feeding session.
 16. The computer program product of claim 10, whereinautomatically certifying whether the product satisfies the claim furthercomprises comparing the event data to a supply record.
 17. The computerprogram product of claim 10, wherein automatically certifying whetherthe product satisfies the claim further comprises linking contaminatedfeed to specific animals or groups of animals.
 18. The computer programproduct of claim 10, wherein the computer program product furthercomprises instructions that, when read by a machine, operate to causedata processing apparatus to: encrypt and decrypt the event data; andperform an authentication operation on the second supply managementdevice, wherein the data conversion interface is established based onsuccessful performance of the authentication operation.
 19. A devicecomprising: a processor configured to automatically certify whether aproduct satisfies a claim, further comprising: establishing a datacollection interface between a first supply management device and atransaction database, the data collection interface providing thetransaction database with access to identification data and event data,the identification data uniquely identifying the product, and the eventdata relating to a feeding process associated with the product,receiving a product tracking request for formatted identification dataor event data from a second supply management device, and establishing adata conversion interface between the second supply management device,and the identification data or the event data, the data conversioninterface providing the second supply management device with access tothe identification data and/or the event data, according to the producttracking request; and an interface configured to output a result of theautomatic certification.
 20. The device of claim 19, wherein the claimis a genetically modified (GM)-free claim or an organic claim.
 21. Thedevice of claim 19, wherein, in outputting the result, the interface isfurther configured to display whether an animal was fed geneticallymodified feed or feed made partial from animal protein components, orwhether a diet of the animal was limited to organic products.
 22. Thedevice of claim 19, wherein, in automatically certifying whether theproduct satisfies the claim, the interface is further configured toautomatically determine whether the product satisfies regulatoryrestrictions.
 23. The device of claim 19, wherein, in automaticallycertifying whether the product satisfies the claim, the processor isfurther configured to causing a third party to certify the product asbeing genetically modified (GM)-free or organic.
 24. The device of claim19, wherein the event data uniquely identifies a particular feed lot ora feeding session.
 25. The device of claim 19, wherein, in automaticallycertifying whether the product satisfies the claim, the processor isfurther configured to compare the event data to a supply record.
 26. Thedevice of claim 19, wherein, in automatically certifying whether theproduct satisfies the claim, the processor is further configured to linkcontaminated feed to specific animals or groups of animals.
 27. Thedevice of claim 19, further comprising: a security module configured to:encrypt and decrypt the event data, and perform an authenticationoperation on the second supply management device, wherein the dataconversion interface is established based on successful performance ofthe authentication operation.